Triple
T13539679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idoma |
E323350
|
entity |
| Predicate | subgroup |
P10
|
FINISHED |
| Object | Utonkon |
E963549
|
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: Utonkon | Statement: [Idoma, subgroup, Utonkon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Utonkon Context triple: [Idoma, subgroup, Utonkon]
-
A.
Utonkon
chosen
Utonkon is a dialect of the Idoma language spoken by a subgroup of the Idoma people in central Nigeria.
-
B.
Uzynagash
Uzynagash is a rural settlement in southeastern Kazakhstan that serves as a local center within the Almaty Region.
-
C.
Tokoro
Tokoro is a coastal district of Kitami City in Hokkaido, Japan, known historically for its fishing industry and drift ice along the Sea of Okhotsk.
-
D.
Ukaan
Ukaan is a little-documented Niger-Congo language spoken by a small community in southwestern Nigeria.
-
E.
Ōtoku
Ōtoku was a Japanese era name (nengō) of the late 11th century, used during the reign of Emperor Shirakawa.
- 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_69f75d9c04b881908a359df791b89b43 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.