Triple
T3106959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Moore’s Creek Bridge |
E64854
|
entity |
| Predicate | PatriotCasualties |
P45977
|
FINISHED |
| Object | 1 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: 1 killed | Statement: [Battle of Moore’s Creek Bridge, PatriotCasualties, 1 killed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PatriotCasualties Context triple: [Battle of Moore’s Creek Bridge, PatriotCasualties, 1 killed]
-
A.
UScasualties
Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
-
B.
casualtiesUnitedStates
Indicates that the event or situation resulted in casualties (deaths and/or injuries) among United States personnel or citizens.
-
C.
NATOcasualtiesMilitaryKilled
Indicates that members of NATO military forces were killed as casualties.
-
D.
confederateCasualtiesAndLosses
Indicates the number or extent of casualties and material losses suffered by Confederate forces in a conflict or engagement.
-
E.
militaryCasualtiesEstimate
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29d4aa8819093287bc71370fc05 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.