Triple
T31854914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allahyar Khan Asaf al-Dowleh |
E813167
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century Iranian politician |
C59068
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: 19th-century Iranian politician Context triple: [Allahyar Khan Asaf al-Dowleh, instanceOf, 19th-century Iranian politician]
-
A.
Iranian statesman
An Iranian statesman is a public figure who plays a significant and often long-term role in shaping Iran’s domestic and foreign policies through political leadership, diplomacy, and governance.
-
B.
Ottoman politician
An Ottoman politician was a statesman or public official within the Ottoman Empire responsible for participating in governance, administration, and policy-making at imperial or provincial levels.
-
C.
Qajar courtier
chosen
A Qajar courtier is a noble or official serving in the royal court of Iran’s Qajar dynasty (1789–1925), engaged in administrative, diplomatic, ceremonial, and advisory roles that supported the shah’s governance and courtly life.
-
D.
Iranian diplomat
An Iranian diplomat is an official representative of the Islamic Republic of Iran who conducts negotiations, manages international relations, and promotes Iran’s political, economic, and cultural interests abroad.
-
E.
Parsi political leader
A Parsi political leader is a public figure of Zoroastrian Parsi heritage who actively participates in governance, policy-making, or political advocacy, representing both broader civic interests and, at times, the concerns of the Parsi community.
- F. None of above.
Provenance (1 batch)
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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:52 p.m.