Triple
T38292614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurgin Khan |
E1022399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Safavid official |
C63882
|
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: Safavid official Context triple: [Gurgin Khan, instanceOf, Safavid official]
-
A.
Timurid official
A Timurid official was an administrative or military functionary serving the Timurid Empire, responsible for implementing imperial policies, managing provincial governance, and maintaining order and revenue collection under the authority of the Timurid rulers.
-
B.
Safavid prince
A Safavid prince is a male member of the royal family of the Safavid dynasty in early modern Iran, typically involved in governance, military leadership, and succession politics within the empire.
-
C.
Ilkhanid official
An Ilkhanid official was an administrative or bureaucratic functionary serving the Ilkhanate (a Mongol-ruled dynasty in Iran and surrounding regions, 13th–14th centuries), responsible for implementing state policies, managing finances, justice, or provincial governance within the empire’s complex multiethnic administration.
-
D.
Qajar courtier
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.
-
E.
Persian court official
A Persian court official is a high-ranking administrator or advisor serving the royal court of ancient or medieval Persia, responsible for managing state affairs, protocol, and governance on behalf of the monarch.
- F. None of above. chosen
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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.