Triple

T2343745
Position Surface form Disambiguated ID Type / Status
Subject Ashkun language E45083 entity
Predicate neighboringLanguages P16383 FINISHED
Object Kati language E228811 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: Kati language | Statement: [Ashkun language, neighboringLanguages, Kati language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kati language
Context triple: [Ashkun language, neighboringLanguages, Kati language]
  • A. Kati language chosen
    The Kati language is a Nuristani language spoken primarily in parts of northeastern Afghanistan and adjacent regions of Pakistan.
  • B. Katu language
    Katu language is an Austroasiatic language spoken by the Katu people primarily in Laos and central Vietnam.
  • C. Kaado language
    The Kaado language is a regional variety within the Songhay language family spoken by communities in parts of West Africa.
  • D. Kalanguya language
    The Kalanguya language is an Austronesian language spoken by the Kalanguya people in the northern Luzon highlands of the Philippines.
  • E. Kaidipang language
    The Kaidipang language is an Austronesian language spoken by the Kaidipang people in northern Sulawesi, Indonesia.
  • 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_69a88917935081909b755dbf38e81024 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abc6ae33e881909a81a0c0def59059 completed March 7, 2026, 6:33 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae96253f0c81908b866c656c3f5bea completed March 9, 2026, 9:43 a.m.
Created at: March 4, 2026, 7:52 p.m.