Triple

T5385821
Position Surface form Disambiguated ID Type / Status
Subject Kay Kavus E120198 entity
Predicate enemy P4567 FINISHED
Object Afrasiab E517727 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: Afrasiab | Statement: [Kay Kavus, enemy, Afrasiab]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Afrasiab
Context triple: [Kay Kavus, enemy, Afrasiab]
  • A. Afrasiab chosen
    Afrasiab is a legendary Turanian king and formidable adversary of Iran in the Persian epic Shahnameh.
  • B. Tushpa
    Tushpa was the ancient fortified city on the eastern shore of Lake Van that served as the political and cultural center of the Kingdom of Urartu in the early first millennium BCE.
  • C. Sarakhs
    Sarakhs is a historic border city in northeastern Iran, known for its strategic location along ancient trade routes between Iran and Central Asia.
  • D. Panjikent
    Panjikent was an important ancient Sogdian city in present-day Tajikistan, known for its well-preserved wall paintings and role as a Silk Road trading center.
  • E. Balkh
    Balkh is an ancient city in northern Afghanistan, historically a major center of Persian culture, trade, and Islamic scholarship.
  • 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_69bd46354c648190a38b26f107010a96 completed March 20, 2026, 1:05 p.m.
NER Named-entity recognition batch_69bd86f6f39c8190aa6af12370e3d12b completed March 20, 2026, 5:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf3a997ad08190acfdd7cc1b396262 completed March 22, 2026, 12:40 a.m.
Created at: March 20, 2026, 2:03 p.m.