Triple
T12503788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 54th Massachusetts Volunteer Infantry Regiment |
E298893
|
entity |
| Predicate | casualtiesAtFortWagner |
P35438
|
FINISHED |
| Object | heavy |
—
|
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: heavy | Statement: [54th Massachusetts Volunteer Infantry Regiment, casualtiesAtFortWagner, heavy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesAtFortWagner Context triple: [54th Massachusetts Volunteer Infantry Regiment, casualtiesAtFortWagner, heavy]
-
A.
confederateCasualtiesAndLosses
Indicates the number or extent of casualties and material losses suffered by Confederate forces in a conflict or engagement.
-
B.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
C.
casualtiesAssociatedWithEvent
chosen
Indicates that certain casualties (deaths or injuries) are linked to, or resulted from, a specific event.
-
D.
UScasualties
Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
-
E.
PatriotCasualties
Indicates that the event involves casualties suffered by patriot forces or supporters.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94dfcea188190a929db1aabe1a286 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d43b7008190af2648fe09fd6d23 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:57 p.m.