Triple
T13539670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idoma |
E323350
|
entity |
| Predicate | traditionalTitle |
P11127
|
FINISHED |
| Object | Och’Idoma |
E1051853
|
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: Och’Idoma | Statement: [Idoma, traditionalTitle, Och’Idoma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Och’Idoma Context triple: [Idoma, traditionalTitle, Och’Idoma]
-
A.
Och’Idoma
chosen
Och’Idoma is the paramount traditional ruler and cultural head of the Idoma people of Benue State in central Nigeria.
-
B.
Igbokoda
Igbokoda is a prominent riverine town in southwestern Nigeria known for its fishing activities and waterways.
-
C.
Ogbolomabiri
Ogbolomabiri is a prominent riverine town within the Nembe area of Bayelsa State in Nigeria, known historically as part of the Nembe Kingdom.
-
D.
Igbo-Ora
Igbo-Ora is a town in southwestern Nigeria widely noted for its unusually high rate of twin births and its predominantly Yoruba (Oyo) cultural heritage.
-
E.
Ndi Orieke
Ndi Orieke is a sub-community within the Ohafia area of Abia State in southeastern Nigeria, known as part of the larger Ohafia cultural and traditional landscape.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafd7ad9481908fe1d7ffcf8fab71 |
completed | April 12, 2026, 2:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78adaf62c8190855df932eb9830be |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:45 p.m.