Triple
T20721621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vyazma defensive operation (1941) |
E509327
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Vyazma |
—
|
NE NERFINISHED |
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: Vyazma | Statement: [Vyazma defensive operation (1941), location, Vyazma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vyazma Context triple: [Vyazma defensive operation (1941), location, Vyazma]
-
A.
Vyazma
chosen
Vyazma is a historic town in Smolensk Oblast, western Russia, known for its strategic military significance, particularly during World War II.
-
B.
Rzhev
Rzhev is a historic town in western Russia known for its strategic location on the Volga River and as the site of major World War II battles.
-
C.
Kozelsk
Kozelsk is a historic town in western Russia known for its medieval defenses and location within Kaluga Oblast.
-
D.
Borisoglebsk
Borisoglebsk is a small Russian city known for its historical architecture and location on the Vorona River in southwestern Russia.
-
E.
Kobryn
Kobryn is a historic town in southwestern Belarus known for its location at the confluence of the Mukhavets and Dnieper–Bug Canal and its role as a regional cultural and economic center.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d6bdcc8190ba42c44159a2c0d5 |
completed | April 21, 2026, 12:16 a.m. |
Created at: April 16, 2026, 12:27 p.m.