Triple
T2031063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umberto II of Italy |
E44516
|
entity |
| Predicate | endOfReignCause |
P15555
|
FINISHED |
| Object | abolition of the monarchy in Italy |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: abolition of the monarchy in Italy | Statement: [Umberto II of Italy, endOfReignCause, abolition of the monarchy in Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfReignCause Context triple: [Umberto II of Italy, endOfReignCause, abolition of the monarchy in Italy]
-
A.
endOfReignReason
chosen
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
-
B.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
C.
reasonForStartOfReign
Indicates the cause, circumstance, or event that led to the beginning of an entity’s reign.
-
D.
reasonForAbdication
Indicates the specific cause, motive, or circumstances that led an individual to formally abdicate a position of authority or power.
-
E.
monarchDeposed
Indicates that a monarch has been removed from power, typically against their will, by force, coercion, or formal deposition.
- F. None of above.
Provenance (3 batches)
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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb915c9548190809d08c4d67466fb |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.