Triple
T6831282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franco-Mauritian |
E157142
|
entity |
| Predicate | settlementPeriod |
P72917
|
FINISHED |
| Object | French colonial era in Mauritius |
—
|
LITERAL 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: French colonial era in Mauritius | Statement: [Franco-Mauritian, settlementPeriod, French colonial era in Mauritius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settlementPeriod Context triple: [Franco-Mauritian, settlementPeriod, French colonial era in Mauritius]
-
A.
settlementTerm
Indicates the agreed conditions, timing, and method by which an obligation, transaction, or dispute is settled between parties.
-
B.
settlementPattern
Indicates how human dwellings or communities are spatially arranged and distributed across a geographic area.
-
C.
settledDate
Indicates the date on which a transaction, obligation, or agreement is fully completed and finalized.
-
D.
possibleSettlementAt
Indicates that a settlement could potentially be established or located at a given place or site.
-
E.
settlementMode
Indicates the method or process by which a financial or transactional obligation is settled or completed between parties.
- F. None of above. chosen
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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62820808190ad3c244893e88699 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d11fab808190b18160ff3829fcc6 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:18 p.m.