Triple

T14468700
Position Surface form Disambiguated ID Type / Status
Subject Qara Khitai E358780 entity
Predicate languageUsed P238 FINISHED
Object Khitan language E723614 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: Khitan language | Statement: [Qara Khitai, languageUsed, Khitan language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khitan language
Context triple: [Qara Khitai, languageUsed, Khitan language]
  • A. Khitan language chosen
    The Khitan language was the now-extinct tongue of the Khitan people of Northeast Asia, written in unique scripts and used by the ruling elite of the Liao dynasty.
  • B. Kangjia language
    The Kangjia language is a lesser-known Mongolic language spoken by the Kangjia people in parts of northwestern China.
  • C. Chulym language
    The Chulym language is a critically endangered Turkic language spoken by a small indigenous community in Siberia, Russia.
  • D. Tsakhur language
    The Tsakhur language is a Northeast Caucasian language spoken primarily by the Tsakhur people in parts of Azerbaijan and Dagestan.
  • E. Buyi language
    The Buyi language is a Tai–Kadai language spoken primarily by the Buyi ethnic group in Guizhou and neighboring regions of southern China.
  • 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_69d827966698819082e140837737501d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de91f8613c819080424104c0b7f4c3 completed April 14, 2026, 7:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd649beec88190861abb52c5a2733e completed May 8, 2026, 4:20 a.m.
Created at: April 10, 2026, 1:20 a.m.