Triple
T21314702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lützen (1632) |
E525434
|
entity |
| Predicate | causeOfDeathOfGustavusAdolphus |
P144
|
FINISHED |
| Object | killed in action while leading cavalry charge |
—
|
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: killed in action while leading cavalry charge | Statement: [Battle of Lützen (1632), causeOfDeathOfGustavusAdolphus, killed in action while leading cavalry charge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDeathOfGustavusAdolphus Context triple: [Battle of Lützen (1632), causeOfDeathOfGustavusAdolphus, killed in action while leading cavalry charge]
-
A.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
B.
SwedishCasualties
Indicates the number or extent of casualties suffered by Swedish forces or individuals in a given event or context.
-
C.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
D.
yearOfKingLudwigIIDeath
Indicates the calendar year in which King Ludwig II died.
-
E.
reasonForDemise
Indicates the cause, circumstance, or factor that led to an entity’s death or termination.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dce6b4081909841ac0440fca5e4 |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:28 p.m.