Triple
T6131277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pahlavi era |
E136723
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | era in 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: era in Iranian history Context triple: [Pahlavi era, instanceOf, era in Iranian history]
-
A.
Iranian legendary dynasty
An Iranian legendary dynasty is a mytho-historical royal lineage in Iranian tradition, often featured in epic literature like the Shahnameh, that symbolizes ideal kingship, cultural values, and the cosmic struggle between good and evil.
-
B.
era in Chinese history
An era in Chinese history is a distinct period marked by characteristic political structures, cultural developments, social changes, and significant events that differentiate it from other historical periods in China.
-
C.
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.
-
D.
era in Russian history
An era in Russian history is a distinct period characterized by specific political structures, social dynamics, cultural developments, and major events that collectively differentiate it from other periods in the nation’s past.
-
E.
era in Swedish history
An era in Swedish history is a distinct period characterized by specific political structures, social conditions, cultural developments, and economic patterns that together define a recognizable phase in Sweden’s historical timeline.
- 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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:15 p.m.