Triple
T37637195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mfengu |
E936519
|
entity |
| Predicate | hasColonialLabel |
P13172
|
FINISHED |
| Object | Fingo |
E936517
|
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: Fingo | Statement: [Mfengu, hasColonialLabel, Fingo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColonialLabel Context triple: [Mfengu, hasColonialLabel, Fingo]
-
A.
hasColonialName
chosen
Indicates that an entity is known by, or has been assigned, a name originating from a colonial power or colonial period.
-
B.
isColonial
Indicates that one entity holds or exhibits colonial status, control, or characteristics in relation to another entity or context.
-
C.
hasColonialForm
Indicates that one entity possesses or exhibits a colonial form or structure in relation to another.
-
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.
hasColonialCity
Indicates that an entity possesses or includes a city that was established or significantly developed during a period of colonial rule.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40ba4c0e2081908c326703c5ed4cc1 |
completed | June 28, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.