Triple

T11685804
Position Surface form Disambiguated ID Type / Status
Subject Western Nilotic languages E277738 entity
Predicate hasMember P10 FINISHED
Object Alur language E231979 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: Alur language | Statement: [Western Nilotic languages, hasMember, Alur language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alur language
Context triple: [Western Nilotic languages, hasMember, Alur language]
  • A. Alur language chosen
    The Alur language is a Western Nilotic language spoken primarily by the Alur people of northwestern Uganda and northeastern Democratic Republic of the Congo.
  • B. Pear language
    Pear language is an Austroasiatic language of the Pearic branch spoken by the Pear people of Cambodia and considered highly endangered.
  • C. Archi language
    The Archi language is a highly complex, morphologically rich Northeast Caucasian language spoken by a small community in southern Dagestan, Russia.
  • D. Soar language
    Soar language is a specialized programming language used to create and manipulate cognitive models within the Soar cognitive architecture.
  • E. Phong language
    The Phong language is a lesser-known Vietic language spoken by an ethnic minority community in Laos.
  • 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_69d6aafe02d881909900d54ad7d4af84 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a463f6448190a4c8e1651a2bd905 completed April 10, 2026, 7:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69ef1433be908190b2ac887655a6c85a completed April 27, 2026, 7:45 a.m.
Created at: April 8, 2026, 9:40 p.m.