Triple

T4549539
Position Surface form Disambiguated ID Type / Status
Subject Seljuk Empire E110127 entity
Predicate notableRuler P22 FINISHED
Object Sanjar E447354 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: Sanjar | Statement: [Seljuk Empire, notableRuler, Sanjar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sanjar
Context triple: [Seljuk Empire, notableRuler, Sanjar]
  • A. Sanjar chosen
    Sanjar was a prominent 12th-century Seljuk ruler who governed the eastern provinces of the empire and is often regarded as its last great sultan.
  • B. Qalat
    Qalat is a key urban center and provincial capital in southern Afghanistan, known for its strategic location and historical fortifications.
  • C. Qala
    Qala is a small village on the eastern tip of the Maltese island of Gozo, known for its scenic coastal views and traditional rural character.
  • D. Gundeshapur
    Gundeshapur was a prominent Sasanian city in southwestern Iran renowned as a major center of learning, medicine, and philosophy in late antiquity.
  • E. Sheberghan
    Sheberghan is a city in northern Afghanistan that serves as a political and military stronghold of Uzbek leader Abdul Rashid Dostum.
  • 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_69bd4412524c8190be5bcc9ddee91848 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd57f3f8348190868e274ac4df87ce completed March 20, 2026, 2:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdb94cab408190956ef333aa810a3b completed March 20, 2026, 9:17 p.m.
Created at: March 20, 2026, 1:05 p.m.