Triple

T9561482
Position Surface form Disambiguated ID Type / Status
Subject Khwarezmian E230683 entity
Predicate alternativeName P39 FINISHED
Object Khorezmian E230683 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: Khorezmian | Statement: [Khwarezmian, alternativeName, Khorezmian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khorezmian
Context triple: [Khwarezmian, alternativeName, Khorezmian]
  • A. Khwarezmian language
    The Khwarezmian language was an extinct East Iranian language once spoken in the historical region of Khwarezm, in present-day Central Asia.
  • B. Sogdians
    The Sogdians were an ancient Iranian people of Central Asia renowned as influential Silk Road merchants and cultural intermediaries between East and West.
  • C. Sogdian language
    The Sogdian language was an Eastern Iranian language once widely used along the Silk Road, especially in trade and religious communities of Central Asia.
  • D. Khwarezmian chosen
    Khwarezmian is an extinct Eastern Iranian language once spoken in the historical region of Khwarezm, in what is now parts of Uzbekistan and Turkmenistan.
  • E. Khorasani Turkic
    Khorasani Turkic is a Turkic language variety spoken primarily in northeastern Iran, especially in the Khorasan region, by Khorasani Turk communities.
  • 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_69ca847e53a88190a60eed7e02257f10 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd994d31e08190b139f5ad10d8ea31 completed April 1, 2026, 10:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69d16144be688190b7120c4f63dc94c3 completed April 4, 2026, 7:06 p.m.
Created at: March 30, 2026, 8:03 p.m.