Triple
T5643582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Battle of Winchester |
E124327
|
entity |
| Predicate | ConfederateCasualties |
P34511
|
FINISHED |
| Object | approximately 250–300 |
—
|
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: approximately 250–300 | Statement: [Second Battle of Winchester, ConfederateCasualties, approximately 250–300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ConfederateCasualties Context triple: [Second Battle of Winchester, ConfederateCasualties, approximately 250–300]
-
A.
confederateCasualtiesAndLosses
chosen
Indicates the number or extent of casualties and material losses suffered by Confederate forces in a conflict or engagement.
-
B.
UScasualties
Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
-
C.
commandingConfederateForces
Indicates that one entity holds the role or responsibility of directing and leading the military operations of the Confederate forces in relation to another entity.
-
D.
hasConfederateBurialCount
Indicates the number of Confederate burials associated with a given entity or site.
-
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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022a7cd9c819087f86f60e8b65fc3 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.