Triple
T21276242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mława |
E524393
|
entity |
| Predicate | strategicObjectiveGermany |
P65762
|
FINISHED |
| Object | break Polish northern defenses |
—
|
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: break Polish northern defenses | Statement: [Battle of Mława, strategicObjectiveGermany, break Polish northern defenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicObjectiveGermany Context triple: [Battle of Mława, strategicObjectiveGermany, break Polish northern defenses]
-
A.
strategicGoalOfGermany
Indicates that something is a strategic goal or long-term objective pursued by Germany.
-
B.
objectiveGermany
Indicates that an entity has Germany as its objective, target, or goal in a given context.
-
C.
PrussianObjective
Indicates that an entity has the goal, target, or strategic objective of achieving or advancing something specifically related to Prussia or Prussian interests.
-
D.
aimOfGermanForces
chosen
Indicates that the specified objective or target is the intended goal or purpose of the actions undertaken by German military forces.
-
E.
strategyUsedByGermany
Indicates that a particular strategy is one that was employed or adopted by Germany.
- 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_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. |
Created at: April 16, 2026, 4:02 p.m.