Triple
T21276241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mława |
E524393
|
entity |
| Predicate | germanForcesRole |
P65762
|
FINISHED |
| Object | offensive advance into Poland |
—
|
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: offensive advance into Poland | Statement: [Battle of Mława, germanForcesRole, offensive advance into Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: germanForcesRole Context triple: [Battle of Mława, germanForcesRole, offensive advance into Poland]
-
A.
combatantRoleOfGermany
Indicates that the specified role is one that Germany held as a combatant in a particular conflict or war.
-
B.
roleInOperationWeserübung
Indicates the specific role or function an entity held in the context of Operation Weserübung.
-
C.
aimOfGermanForces
chosen
Indicates that the specified objective or target is the intended goal or purpose of the actions undertaken by German military forces.
-
D.
germanUnit
Indicates that an entity is a military or organizational unit that belongs to, originates from, or is associated with Germany.
-
E.
GermanLoss
Indicates that Germany experiences a loss, defeat, or negative outcome in the specified context 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_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.