Triple
T14451163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Lorraine in Tuscany |
E358336
|
entity |
| Predicate | lostPowerDueTo |
P86927
|
FINISHED |
| Object | Italian unification |
—
|
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: Italian unification | Statement: [House of Lorraine in Tuscany, lostPowerDueTo, Italian unification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostPowerDueTo Context triple: [House of Lorraine in Tuscany, lostPowerDueTo, Italian unification]
-
A.
lostPowerThrough
chosen
Indicates that an entity ceased to have power, authority, or control as a result of another specified entity or factor.
-
B.
lostPower
Indicates that an entity has ceased to have electrical or functional power it previously possessed.
-
C.
lostPowerIn
Indicates that an entity has experienced a loss of electrical or functional power while in or at a specified location or context.
-
D.
lostPowerDuring
Indicates that an entity ceased to have electrical or functional power at some time during a specified event or interval.
-
E.
lossOfPower
Indicates that an entity experiences a reduction or complete removal of its ability to exert control, influence, or operational capability.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de916244948190bb09d1bfc485ba50 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.