Triple
T33768451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hossein Qoli Khan Qajar |
E865304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iranian noble |
C60154
|
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: Iranian noble Context triple: [Hossein Qoli Khan Qajar, instanceOf, Iranian noble]
-
A.
Sasanian noble
A Sasanian noble is a high-ranking member of the aristocratic elite in the Sasanian Empire, holding hereditary land, military, and administrative privileges that underpin imperial governance and social hierarchy.
-
B.
Achaemenid noble
An Achaemenid noble is a high-ranking member of the Persian aristocracy who held land, military command, and administrative authority under the Achaemenid Empire, often serving as a close supporter and regional representative of the Great King.
-
C.
Iranian noblewoman
An Iranian noblewoman is a high-status female member of Iran’s aristocracy, historically distinguished by lineage, wealth, social influence, and often involvement in political, cultural, or philanthropic affairs.
-
D.
Afghan noble
An Afghan noble is a high-ranking member of Afghanistan’s traditional aristocracy, typically possessing hereditary titles, land, and social influence within tribal or urban elite structures.
-
E.
Iranian royal
An Iranian royal is a member of Iran’s ruling or formerly ruling dynasties, holding hereditary status, titles, and influence within the country’s monarchical tradition.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.