Triple
T21276240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mława |
E524393
|
entity |
| Predicate | polishForcesRole |
P143473
|
FINISHED |
| Object | defending prepared fortifications |
—
|
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: defending prepared fortifications | Statement: [Battle of Mława, polishForcesRole, defending prepared fortifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: polishForcesRole Context triple: [Battle of Mława, polishForcesRole, defending prepared fortifications]
-
A.
PolishUnit
Indicates that a unit is associated with Poland, typically by nationality, origin, or affiliation.
-
B.
PolishCommander
Indicates that an entity serves as a military commander associated with Poland.
-
C.
aimOfPolishSide
Indicates that something represents the goal, intention, or objective pursued by the Polish side in a given context or interaction.
-
D.
PolishCasualties
Indicates the number or extent of casualties suffered by Polish forces or population in a given conflict or event.
-
E.
rolaWZimnejWojnie
Indicates a role or involvement that one entity had in the context of the Cold War.
- F. None of above. chosen
Provenance (4 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736577fd48190a0038a6ac5678668 |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 4:02 p.m.