Triple
T17795543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of New Market |
E444280
|
entity |
| Predicate | cadetCasualties |
P128946
|
FINISHED |
| Object | 10 VMI cadets killed |
—
|
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: 10 VMI cadets killed | Statement: [Battle of New Market, cadetCasualties, 10 VMI cadets killed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cadetCasualties Context triple: [Battle of New Market, cadetCasualties, 10 VMI cadets killed]
-
A.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
B.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
C.
UScasualties
Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
-
D.
casualtiesAssociatedWithEvent
Indicates that certain casualties (deaths or injuries) are linked to, or resulted from, a specific event.
-
E.
casualtiesDescription
Indicates a textual description of the human losses (such as deaths, injuries, or missing persons) resulting from an event or incident.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487fafc2c8190b28e791267c47e3c |
completed | April 19, 2026, 7:44 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:13 a.m.