Triple

T1945899
Position Surface form Disambiguated ID Type / Status
Subject Austroasiatic E42054 entity
Predicate hasLanguage P15 FINISHED
Object Khasi language E216900 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: Khasi language | Statement: [Austroasiatic, hasLanguage, Khasi language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khasi language
Context triple: [Austroasiatic, hasLanguage, Khasi language]
  • A. Khasi language chosen
    Khasi language is an Austroasiatic language spoken primarily in the northeastern Indian state of Meghalaya by the Khasi people.
  • B. Karbi language
    The Karbi language is a Tibeto-Burman language spoken primarily by the Karbi people in Northeast India, especially in Assam.
  • C. Chakma language
    The Chakma language is an Indo-Aryan language spoken primarily by the Chakma people of Bangladesh and northeastern India.
  • D. Lepcha language
    The Lepcha language is an indigenous Sino-Tibetan language spoken primarily by the Lepcha people in parts of Sikkim and neighboring regions of India, Bhutan, and Nepal, known for its unique script and rich oral tradition.
  • E. Pa’O language
    The Pa’O language is a Tibeto-Burman language spoken primarily by the Pa’O (Taungthu) people of Myanmar, especially in Shan and Kayin States.
  • 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_69ae03180a248190a0df96066923728a completed March 8, 2026, 11:15 p.m.
Created at: March 4, 2026, 7:36 p.m.