Triple
T10540106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Frezenberg |
E248671
|
entity |
| Predicate | alliedCasualties |
P17247
|
FINISHED |
| Object | tens of thousands |
—
|
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: tens of thousands | Statement: [Battle of Frezenberg, alliedCasualties, tens of thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliedCasualties Context triple: [Battle of Frezenberg, alliedCasualties, tens of thousands]
-
A.
casualtiesAllied
chosen
Indicates the number or extent of losses (killed, wounded, or missing) suffered by allied forces in a conflict or incident.
-
B.
UScasualties
Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
-
C.
casualtiesUnion
Indicates a relationship where multiple casualty figures or reports are combined into a single aggregated total.
-
D.
englishCasualtiesKilledAndWounded
Indicates the number of English individuals who were either killed or wounded as a result of a particular event or conflict.
-
E.
militaryCasualtiesSide
Indicates the side or party in a conflict to which the recorded military casualties belong.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a582be48190856c6f272eea4dcf |
completed | April 7, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:32 p.m.