Triple
T14574952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulrich, Duke of Württemberg |
E342017
|
entity |
| Predicate | restorationToPower |
P3245
|
FINISHED |
| Object | 1534 |
—
|
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: 1534 | Statement: [Ulrich, Duke of Württemberg, restorationToPower, 1534]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restorationToPower Context triple: [Ulrich, Duke of Württemberg, restorationToPower, 1534]
-
A.
regainedPowerAgainIn
chosen
Indicates that an entity, having previously lost power, has once more returned to a position of power or control within a specified context or location.
-
B.
regainedPowerIn
Indicates that an entity has recovered or reestablished its previous level of power, control, or authority within a specified context or domain.
-
C.
lostPowerAfter
Indicates that one entity ceased to have power or electricity following an event associated with another entity.
-
D.
restored
Indicates that an entity has returned another entity to a previous or improved state, condition, or position after damage, loss, or alteration.
-
E.
lostPowerAgainIn
Indicates that an entity has experienced a repeated loss of power in a specified location or context.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f49d58819094fcd2a702e146cb |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.