Triple
T1431113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lowestoft |
E30447
|
entity |
| Predicate | dutchCasualtiesKilledAndWounded |
P6773
|
FINISHED |
| Object | approximately 4,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: approximately 4,000 | Statement: [Battle of Lowestoft, dutchCasualtiesKilledAndWounded, approximately 4,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dutchCasualtiesKilledAndWounded Context triple: [Battle of Lowestoft, dutchCasualtiesKilledAndWounded, approximately 4,000]
-
A.
NATOcasualtiesMilitaryKilled
Indicates that members of NATO military forces were killed as casualties.
-
B.
PolishCasualties
Indicates the number or extent of casualties suffered by Polish forces or population in a given conflict or event.
-
C.
militaryCasualtiesEstimate
chosen
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
-
D.
livestockLostNetherlands
Indicates livestock that have died or gone missing within the Netherlands, typically as a net loss count over a given period.
-
E.
numberOfGermanVictims
Indicates the quantity of victims who are identified as German in the context of the described event or situation.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.