Triple

T13298028
Position Surface form Disambiguated ID Type / Status
Subject Simbu Province E316735 entity
Predicate localLanguage P1252 FINISHED
Object Kuman language E619329 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: Kuman language | Statement: [Simbu Province, localLanguage, Kuman language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kuman language
Context triple: [Simbu Province, localLanguage, Kuman language]
  • A. Cuman language
    Cuman language is an extinct Kipchak Turkic language once spoken by the nomadic Cuman people across the Eurasian steppe in the Middle Ages.
  • B. Kumandin language
    The Kumandin language is a Turkic language spoken by the Kumandin people of the Altai region in Russia, belonging to the Kipchak branch.
  • C. Kumzari language
    The Kumzari language is an endangered Southwestern Iranian language spoken primarily by the Kumzari people in the Musandam Peninsula of Oman.
  • D. Kumil language chosen
    The Kumil language is a lesser-known Papuan language spoken by the Bel people of Papua New Guinea.
  • E. Khumi language
    The Khumi language is a lesser-known Tibeto-Burman language spoken primarily by the Khumi people in parts of Myanmar and neighboring regions.
  • 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_69d806b40ab4819094adf6c374f4811a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d990a2f2708190a8f2aa7e7c0b92d2 completed April 11, 2026, 12:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69f716dd0cd88190b0ae81b402fc31cf completed May 3, 2026, 9:35 a.m.
Created at: April 9, 2026, 9:28 p.m.