Triple

T14786448
Position Surface form Disambiguated ID Type / Status
Subject Anuak language E347537 entity
Predicate neighboringLanguages P16383 FINISHED
Object Opo language E865593 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: Opo language | Statement: [Anuak language, neighboringLanguages, Opo language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Opo language
Context triple: [Anuak language, neighboringLanguages, Opo language]
  • A. Opuo language chosen
    Opuo is a Koman language spoken by a small ethnic group in parts of Ethiopia and South Sudan, known for its highly endangered status and limited documentation.
  • B. Oepao language
    The Oepao language is an Austronesian language spoken on Rote Island in Indonesia, belonging to the Rote subgroup of the Timoric branch.
  • C. Opokuma language
    The Opokuma language is a Niger-Congo language spoken by the Opokuma subgroup of the Ijaw people in Nigeria’s Niger Delta region.
  • D. Opata language
    The Opata language is an extinct Uto-Aztecan language once spoken by the Opata people of northern Mexico, particularly in the present-day state of Sonora.
  • E. Pokomo language
    The Pokomo language is a Bantu language spoken primarily by the Pokomo people along Kenya’s Tana River.
  • 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_69d822e9b9e08190bedcc31a163fda82 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69decaa083e481908336d58d026eec32 completed April 14, 2026, 11:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe24b9e8a08190bc736ac207b77324 completed May 8, 2026, 6 p.m.
Created at: April 10, 2026, 1:31 a.m.