Triple
T12401173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Igboid languages |
E296255
|
entity |
| Predicate | containsLanguage |
P2177
|
FINISHED |
| Object | Ekpeye language |
E972785
|
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: Ekpeye language | Statement: [Igboid languages, containsLanguage, Ekpeye language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ekpeye language Context triple: [Igboid languages, containsLanguage, Ekpeye language]
-
A.
Ekpeye language
chosen
Ekpeye language is a Niger-Congo language spoken by the Ekpeye people of Rivers State in southern Nigeria.
-
B.
Teke-Kukuya language
The Teke-Kukuya language is a Bantu language spoken by the Teke-Kukuya people in the Republic of the Congo and neighboring regions of Central Africa.
-
C.
Nupe language
The Nupe language is a Niger-Congo language spoken primarily by the Nupe people in central Nigeria, especially in the Middle Belt region.
-
D.
Ikwerre language
Ikwerre language is an Igboid language spoken primarily by the Ikwerre people in Rivers State, Nigeria.
-
E.
Keapara language
The Keapara language is an Austronesian language of coastal Papua New Guinea spoken by the Keapara people in Central Province.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94d46007c81908e0f4b590402bf58 |
completed | April 10, 2026, 7:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f63482af8c8190b277b36371979f5e |
completed | May 2, 2026, 5:29 p.m. |
Created at: April 8, 2026, 9:55 p.m.