Triple
T22765682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Craonne |
E563115
|
entity |
| Predicate | CoalitionCasualtiesApprox |
P6773
|
FINISHED |
| Object | about 5,000–9,000 |
—
|
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: about 5,000–9,000 | Statement: [Battle of Craonne, CoalitionCasualtiesApprox, about 5,000–9,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CoalitionCasualtiesApprox Context triple: [Battle of Craonne, CoalitionCasualtiesApprox, about 5,000–9,000]
-
A.
coalitionCasualties
Indicates that members of a coalition have suffered deaths or injuries as a result of a particular conflict, event, or action.
-
B.
militaryCasualtiesSide
Indicates the side or party in a conflict to which the recorded military casualties belong.
-
C.
casualtiesUnion
Indicates a relationship where multiple casualty figures or reports are combined into a single aggregated total.
-
D.
militaryCasualtiesEstimate
chosen
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
-
E.
NATOcasualtiesMilitaryKilled
Indicates that members of NATO military forces were killed as casualties.
- 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a80249c819091569e7b8d500b45 |
completed | April 29, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:26 p.m.