Triple
T13038326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Vyazma |
E326621
|
entity |
| Predicate | strategyUsedByGermany |
P108400
|
FINISHED |
| Object | pincer movement |
—
|
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: pincer movement | Statement: [Battle of Vyazma, strategyUsedByGermany, pincer movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategyUsedByGermany Context triple: [Battle of Vyazma, strategyUsedByGermany, pincer movement]
-
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.
combatantRoleOfGermany
Indicates that the specified role is one that Germany held as a combatant in a particular conflict or war.
-
D.
GermanLoss
Indicates that Germany experiences a loss, defeat, or negative outcome in the specified context or event.
-
E.
PrussianStrength
Indicates a relationship where an entity possesses or exhibits the military, political, or institutional power characteristic of Prussia.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
| PDg | Predicate description generation | batch_69d98a9577d081908ddef9ea77e408e2 |
completed | April 10, 2026, 11:41 p.m. |
Created at: April 9, 2026, 8:55 p.m.