Triple

T14822981
Position Surface form Disambiguated ID Type / Status
Subject Tahmasp II E348501 entity
Predicate deathPlace P21 FINISHED
Object Sabzevar E338361 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: Sabzevar | Statement: [Tahmasp II, deathPlace, Sabzevar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sabzevar
Context triple: [Tahmasp II, deathPlace, Sabzevar]
  • A. Sabzevar chosen
    Sabzevar is a historic and economically significant city in northeastern Iran, known as a regional center of trade, agriculture, and culture in the Khorasan area.
  • B. Bavanat
    Bavanat is a small city in southern Iran known for its traditional rural landscapes, gardens, and location within the mountainous region of Fars Province.
  • C. Shahrud
    Shahrud is a major city in northeastern Iran known as an important regional hub for transportation, agriculture, and access to nearby natural attractions such as the Alborz Mountains and desert landscapes.
  • D. Zaranj
    Zaranj is a key border city in southwestern Afghanistan that serves as an important trade and transit hub with neighboring Iran.
  • E. Shahreza
    Shahreza is a city in central Iran, known for its historical significance and location along major transit routes in Isfahan Province.
  • 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_69d822eb8f588190bf53445e730a934f completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69decfe7a8dc8190bcb5ecfa1cbf1601 completed April 14, 2026, 11:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe389d7c848190813be06bed7813d7 completed May 8, 2026, 7:25 p.m.
Created at: April 10, 2026, 1:51 a.m.