Triple

T14050855
Position Surface form Disambiguated ID Type / Status
Subject Ado E338084 entity
Predicate hasCommonLanguage P741 FINISHED
Object Idoma language E286633 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: Idoma language | Statement: [Ado, hasCommonLanguage, Idoma language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Idoma language
Context triple: [Ado, hasCommonLanguage, Idoma language]
  • A. Idoma language chosen
    The Idoma language is a major Niger-Congo language spoken primarily by the Idoma people in central Nigeria, especially in Benue State.
  • B. Igala language
    Igala language is a Niger-Congo language spoken primarily in central Nigeria by the Igala people, closely related to Yoruba and other Defoid languages.
  • C. Ikposo language
    The Ikposo language is a Niger-Congo language spoken by the Akposso people of Togo and neighboring regions.
  • D. Okpamheri language
    The Okpamheri language is a lesser-known Edoid language spoken by a small ethnic community in southern Nigeria.
  • E. Ikare-Akoko language
    The Ikare-Akoko language is a Yoruboid language variety spoken primarily in and around the town of Ikare-Akoko in southwestern Nigeria.
  • 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_69d81c664e48819088cbd8f433aeffe5 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de3c8a518081908ad030ba48b7b946 completed April 14, 2026, 1:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcdefaabd0819098870522a6ce850c completed May 7, 2026, 6:50 p.m.
Created at: April 9, 2026, 10:20 p.m.