Triple
T22522071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Vågen |
E556804
|
entity |
| Predicate | DutchCasualties |
P34639
|
FINISHED |
| Object | light |
—
|
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: light | Statement: [Battle of Vågen, DutchCasualties, light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DutchCasualties Context triple: [Battle of Vågen, DutchCasualties, light]
-
A.
dutchCasualties
chosen
Indicates that the relationship specifies the number or occurrence of casualties suffered by Dutch entities in a given event or context.
-
B.
PolishCasualties
Indicates the number or extent of casualties suffered by Polish forces or population in a given conflict or event.
-
C.
DanishCasualtiesApprox
Indicates an approximate number of Danish individuals who were killed, wounded, or otherwise counted as casualties in a specific event or context.
-
D.
BoerCasualties
Indicates the number or occurrence of casualties suffered by Boer forces in a conflict or engagement.
-
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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e32b8a88190ac335d4298dd5ee3 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.