Triple

T23175064
Position Surface form Disambiguated ID Type / Status
Subject Kulisusu–Koroni cluster E578973 entity
Predicate hasMember P10 FINISHED
Object Taloki language NE NERFINISHED

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: Taloki language | Statement: [Kulisusu–Koroni cluster, hasMember, Taloki language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Taloki language
Context triple: [Kulisusu–Koroni cluster, hasMember, Taloki language]
  • A. Talni language
    The Talni language is a lesser-known Niger-Congo language of the Southern Gur branch, spoken by a small community in West Africa.
  • B. Tialo language
    The Tialo language is an Austronesian language spoken in Central Sulawesi, Indonesia, as part of the Tomini subgroup.
  • C. Tolaki language chosen
    The Tolaki language is an Austronesian language spoken by the Tolaki people of southeastern Sulawesi, Indonesia.
  • D. Talodi languages
    The Talodi languages are a small group of closely related Niger–Congo languages spoken mainly in the Nuba Mountains of Sudan.
  • E. Tal language
    Tal language is a minor Chadic language spoken in central Nigeria, belonging to the Angas–Sura subgroup of the West Chadic branch of the Afroasiatic language family.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245fd2a388190b814c0dfa15f7148 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18f69cb1881909e0f47d3b32e2cb1 completed April 29, 2026, 4:56 a.m.
Created at: April 17, 2026, 4:04 p.m.