Triple

T13539645
Position Surface form Disambiguated ID Type / Status
Subject Idoma E323350 entity
Predicate languageFamily P1047 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: [Idoma, languageFamily, Idoma language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Idoma language
Context triple: [Idoma, languageFamily, 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_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_69f76babfb948190bc028450ddaa0b72 completed May 3, 2026, 3:37 p.m.
Created at: April 9, 2026, 9:45 p.m.