Triple
T24424356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mauritian dollar |
E615814
|
entity |
| Predicate | formerColonialContext |
P47818
|
FINISHED |
| Object | British Empire |
—
|
NE NERFINISHED |
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: British Empire | Statement: [Mauritian dollar, formerColonialContext, British Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerColonialContext Context triple: [Mauritian dollar, formerColonialContext, British Empire]
-
A.
formerColonialEntity
chosen
Indicates that one entity was previously a colony or colonial possession of another entity.
-
B.
isColonial
Indicates that one entity holds or exhibits colonial status, control, or characteristics in relation to another entity or context.
-
C.
formerColonialStatus
Indicates that one entity previously held colonial authority or control over another entity, but that colonial relationship has since ended.
-
D.
hasColonialHistory
Indicates that an entity has experienced or participated in a period of colonial rule, control, or administration in relation to another entity.
-
E.
previousColonialInvolvement
Indicates that one entity had a colonial role or presence in another entity at some time in the past.
- F. None of above.
Provenance (3 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a4e3e4819094ac0941da5ca641 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:14 a.m.