Triple
T11738820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Chalgrove Field |
E279099
|
entity |
| Predicate | HampdenDiedFromWounds |
P101085
|
FINISHED |
| Object | 24 June 1643 |
—
|
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: 24 June 1643 | Statement: [Battle of Chalgrove Field, HampdenDiedFromWounds, 24 June 1643]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HampdenDiedFromWounds Context triple: [Battle of Chalgrove Field, HampdenDiedFromWounds, 24 June 1643]
-
A.
killedOrMortallyWounded
Indicates that one entity caused the death of, or inflicted injuries certain to result in the death of, another entity.
-
B.
BritishCommanderKilledInAction
Indicates that a British military commander was killed while actively engaged in combat operations.
-
C.
notableCommanderKilledInAction
Indicates that a notable military commander associated with an entity was killed in action.
-
D.
discoveredAsDeadBy
Indicates that one entity was found to be dead by another entity, who discovered their deceased state.
-
E.
wasWoundedIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or conflict.
- F. None of above. chosen
Provenance (4 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4ef1c4881909ad36dc27b1fe193 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.