Triple
T9124641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danish constitutional crisis of 1848 |
E218941
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Danish history |
C25643
|
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 Danish history Context triple: [Danish constitutional crisis of 1848, instanceOf, event in Danish history]
-
A.
event in British history
A significant occurrence or series of actions within the geographical and political context of Britain that influenced its social, political, economic, or cultural development and is recognized as part of its historical narrative.
-
B.
event in Irish history
An event in Irish history is a significant occurrence or series of actions within Ireland’s past that influenced its political, social, cultural, or economic development.
-
C.
event in Serbian history
A significant occurrence or development within the historical timeline of Serbia that influenced its political, social, cultural, or territorial evolution.
-
D.
medieval event
A medieval event is a historically themed gathering or occurrence set in or inspired by the Middle Ages, often featuring period-appropriate customs, attire, activities, and social structures.
-
E.
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.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:17 p.m.