Triple

T11685825
Position Surface form Disambiguated ID Type / Status
Subject Western Nilotic languages E277738 entity
Predicate hasMember P10 FINISHED
Object Lugbara language E262849 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: Lugbara language | Statement: [Western Nilotic languages, hasMember, Lugbara language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lugbara language
Context triple: [Western Nilotic languages, hasMember, Lugbara language]
  • A. Lugbara language chosen
    The Lugbara language is a Central Sudanic language spoken primarily by the Lugbara people of northwestern Uganda and northeastern Democratic Republic of the Congo.
  • B. Lusoga language
    The Lusoga language is a Bantu language spoken primarily by the Basoga people in eastern Uganda.
  • C. Lunda language
    The Lunda language is a Bantu language spoken primarily in parts of Angola, the Democratic Republic of the Congo, and Zambia by the Lunda people.
  • D. Tembe language
    The Tembe language is an indigenous Tupi-Guarani language spoken by the Tembé people of northern Brazil.
  • E. Nsenga language
    The Nsenga language is a Bantu language spoken primarily in Zambia and neighboring regions, closely related to other languages of the area such as Tumbuka and Chewa.
  • 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.