Triple
T36382175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Louis District |
E896075
|
entity |
| Predicate | hasCommercialCenterOf |
P79077
|
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, hasCommercialCenterOf, Mauritius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommercialCenterOf Context triple: [Port Louis District, hasCommercialCenterOf, Mauritius]
-
A.
hasCommercialCenterType
Indicates that an entity has or is associated with a specific type or category of commercial center (e.g., mall, shopping district, business park).
-
B.
hasMajorCommercialCentre
chosen
Indicates that a place contains or hosts a primary hub of significant commercial or business activity.
-
C.
isTransportCenterOf
Indicates that a location functions as a primary hub or central node for transportation activities serving another area or network.
-
D.
isTownCenterOf
Indicates that a location functions as the central, primary area or hub of a specified town.
-
E.
isCommercialCapitalOf
Indicates that a location serves as the primary center of commerce, trade, or business activity for another region or entity.
- 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_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbbc4f9081909f83c4fc506083cf |
completed | June 23, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.