Triple

T1945911
Position Surface form Disambiguated ID Type / Status
Subject Austroasiatic E42054 entity
Predicate hasLanguage P15 FINISHED
Object Katu language E216902 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: Katu language | Statement: [Austroasiatic, hasLanguage, Katu language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Katu language
Context triple: [Austroasiatic, hasLanguage, Katu language]
  • A. Katu language chosen
    Katu language is an Austroasiatic language spoken by the Katu people primarily in Laos and central Vietnam.
  • B. Kawaiisu language
    Kawaiisu language is an endangered Uto-Aztecan language traditionally spoken by the Kawaiisu people of southern California.
  • C. Bugotu language
    The Bugotu language is an Oceanic language spoken by the Bugotu people of Santa Isabel Island in the Solomon Islands.
  • D. Kioko language
    The Kioko language is an Austronesian language of the Muna–Buton subgroup spoken by a small community in southeastern Sulawesi, Indonesia.
  • E. Kaado language
    The Kaado language is a regional variety within the Songhay language family spoken by communities in parts of West Africa.
  • 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_69a8870e08fc8190a319cbf2600db15f completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb300af2481908ae359972843c1ef completed March 7, 2026, 5:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69adfbbcc5688190aad081dc8d119e7f completed March 8, 2026, 10:44 p.m.
Created at: March 4, 2026, 7:36 p.m.