Triple
T29397108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lidzbark Warmiński |
E745528
|
entity |
| Predicate | RussianPrussianCasualtiesApprox |
P6773
|
FINISHED |
| Object | 11000 |
—
|
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: 11000 | Statement: [Battle of Lidzbark Warmiński, RussianPrussianCasualtiesApprox, 11000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RussianPrussianCasualtiesApprox Context triple: [Battle of Lidzbark Warmiński, RussianPrussianCasualtiesApprox, 11000]
-
A.
RussianPrussianStrengthApprox
Indicates that the strength or power of Russian and Prussian forces is approximately equal or comparable.
-
B.
militaryCasualtiesSide
Indicates the side or party in a conflict to which the recorded military casualties belong.
-
C.
militaryCasualtiesEstimate
chosen
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
-
D.
PrussianStrengthApprox
Indicates an approximate assessment or estimation of the strength or power associated with Prussia in a given context.
-
E.
PolishCasualties
Indicates the number or extent of casualties suffered by Polish forces or population in a given conflict or event.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a0486448190aad3372000e53ebb |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 2:47 p.m.