Triple
T9054968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rise and fall of Elagabalus |
E216974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical event sequence |
C1636
|
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: historical event sequence Context triple: [Rise and fall of Elagabalus, instanceOf, historical event sequence]
-
A.
historical process
chosen
A historical process is a sequence of interconnected events and developments over time through which social, political, economic, or cultural conditions gradually change.
-
B.
event in ancient history
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.
-
C.
history organization
A history organization is an entity dedicated to researching, preserving, interpreting, and promoting understanding of past events, cultures, and narratives through activities such as archiving, education, and public outreach.
-
D.
historical event aftermath
The historical event aftermath is the period and set of consequences that follow a significant occurrence, encompassing its social, political, economic, and cultural impacts over time.
-
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_69ca83d4425481909a319dab847724ec |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:10 p.m.