Triple
T3106961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Moore’s Creek Bridge |
E64854
|
entity |
| Predicate | LoyalistCasualties |
P39453
|
FINISHED |
| Object | dozens 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: dozens killed | Statement: [Battle of Moore’s Creek Bridge, LoyalistCasualties, dozens killed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LoyalistCasualties Context triple: [Battle of Moore’s Creek Bridge, LoyalistCasualties, dozens killed]
-
A.
loyalistsBase
Indicates that a group of loyalists is based at, or primarily operates from, a particular location or base.
-
B.
loyalistUnitOf
Indicates that one unit is a loyal or devoted supporter, follower, or subordinate of another entity.
-
C.
casualties_British_side
chosen
Indicates the number or extent of casualties suffered by the British side in a conflict or incident.
-
D.
casualtiesUnion
Indicates a relationship where multiple casualty figures or reports are combined into a single aggregated total.
-
E.
coalitionCasualties
Indicates that members of a coalition have suffered deaths or injuries as a result of a particular conflict, event, or action.
- 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_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. |
Created at: March 8, 2026, 3:04 p.m.