Triple
T14651735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achaemenid succession crisis of 522 BCE |
E344003
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in ancient Persia |
C13438
|
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: event in ancient Persia Context triple: [Achaemenid succession crisis of 522 BCE, instanceOf, event in ancient Persia]
-
A.
event in ancient history
chosen
An event in ancient history is a significant occurrence or series of actions that took place in early human civilizations and has had a lasting impact on cultural, political, or social development.
-
B.
era in Iranian history
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.
-
C.
Mesopotamian festival
A Mesopotamian festival is a recurring religious and civic celebration in ancient Mesopotamia that honored specific deities through rituals, processions, offerings, and communal feasting, reinforcing cosmic order and social cohesion.
-
D.
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.
-
E.
Achaemenid institution
An Achaemenid institution is an organized structure or system—political, administrative, religious, economic, or military—established and maintained by the Achaemenid Empire to govern, manage resources, and integrate its diverse territories.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:27 a.m.