Triple

T10247915
Position Surface form Disambiguated ID Type / Status
Subject Teke languages E240265 entity
Predicate hasMember P10 FINISHED
Object Teke-Eboo language E853704 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: Teke-Eboo language | Statement: [Teke languages, hasMember, Teke-Eboo language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Teke-Eboo language
Context triple: [Teke languages, hasMember, Teke-Eboo language]
  • A. Teke-Eboo languages chosen
    The Teke-Eboo languages are a subgroup of Bantu languages spoken primarily by Teke-related communities in Central Africa, especially in the Republic of the Congo and surrounding regions.
  • B. Kaera language
    The Kaera language is a Papuan language spoken by a small community on Pantar Island in eastern Indonesia.
  • C. Karkar-Yuri language
    Karkar-Yuri is a Papuan language of Papua New Guinea, spoken by the Karkar and Yuri peoples in the Sepik region.
  • D. Lo-Toga language
    The Lo-Toga language is an Oceanic language spoken on the Torres Islands of northern Vanuatu, closely related to the neighboring Hiw language and known for its highly conservative phonology and grammar.
  • E. Saraveca language
    The Saraveca language is an extinct Arawakan language once spoken in Bolivia, known from very limited historical documentation.
  • 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_69d381a7e198819090280d5ab885d59e completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d22e0d4c8190a6712859924e9d3d completed April 7, 2026, 9:45 a.m.
NED1 Entity disambiguation (via context triple) batch_69d71cbd67648190ba7faebd12d96ca9 completed April 9, 2026, 3:27 a.m.
Created at: April 6, 2026, 11:27 a.m.