Triple
T36382174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Louis District |
E896075
|
entity |
| Predicate | hasMainPortOf |
P53991
|
FINISHED |
| Object | Mauritius |
E28590
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Mauritius | Statement: [Port Louis District, hasMainPortOf, Mauritius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainPortOf Context triple: [Port Louis District, hasMainPortOf, Mauritius]
-
A.
hasMainPortal
Indicates that one entity serves as the primary or main portal (entry point or access interface) for another entity.
-
B.
isHomePortOf
Indicates that a particular location serves as the primary base or port where a vessel or fleet is officially registered, stationed, or regularly returns.
-
C.
isMainDeepWaterPortFor
chosen
Indicates that one location serves as the primary deep-water port facility for another entity, such as a region, city, or country.
-
D.
isPortOf
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
-
E.
isMainHarbourOf
Indicates that a harbour serves as the primary or principal port facility for a specified location or region.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0338d1074481909541e6150307e7f8 |
completed | May 12, 2026, 2:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfbd75e08190a11fd7c2672a8556 |
completed | June 23, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_6a03386e7da08190b533cb0e908503dd |
completed | May 12, 2026, 2:25 p.m. |
Created at: May 3, 2026, 4:10 p.m.