Triple
T34818028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zand era |
E1003690
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | period of Iranian history |
C19978
|
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: period of Iranian history Context triple: [Zand era, instanceOf, period of Iranian history]
-
A.
era in Iranian history
chosen
An era in Iranian history is a distinct period characterized by specific political structures, cultural developments, social dynamics, and major events that collectively define a recognizable phase in the historical evolution of Iran.
-
B.
era of Islamic history
An era of Islamic history is a distinct period characterized by particular political structures, cultural developments, religious thought, and social dynamics within the broader historical trajectory of Muslim societies.
-
C.
ancient Iranian dynasty
An ancient Iranian dynasty is a long-ruling hereditary line of monarchs originating in the Iranian cultural sphere that governed significant territories in antiquity, shaping the region’s political, social, and religious history.
-
D.
medieval Iranian state
A medieval Iranian state is a historically situated political entity in the Iranian plateau and surrounding regions, characterized by dynastic rule, Persianate administrative and cultural traditions, and interaction with neighboring Islamic and Eurasian powers between roughly the 7th and 15th centuries.
-
E.
historical period
A historical period is a span of time characterized by distinct social, political, cultural, or technological conditions that differentiate it from other eras in history.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 4 p.m.