Triple
T12720597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Velikiye Luki |
E303967
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Velikiye Luki |
E324832
|
NE 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: Velikiye Luki | Statement: [Battle of Velikiye Luki, location, Velikiye Luki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Velikiye Luki Context triple: [Battle of Velikiye Luki, location, Velikiye Luki]
-
A.
Velikiye Luki
chosen
Velikiye Luki is a city in western Russia known for being the site of a major World War II battle on the Eastern Front.
-
B.
Volzhsky
Volzhsky is a major industrial city in southwestern Russia located across the Volga River from Volgograd.
-
C.
Tikhvin
Tikhvin is a historic town in northwestern Russia known for its ancient monastery, religious icons, and role as a regional cultural and industrial center.
-
D.
Volzhsk
Volzhsk is an industrial city in the Republic of Mari El, Russia, located on the Volga River and known for its manufacturing and river transport significance.
-
E.
Zaraysk
Zaraysk is a historic town in Moscow Oblast, Russia, known for its well-preserved medieval kremlin and role as a former regional administrative center.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d964133fe481909a44b8159ab8997b |
completed | April 10, 2026, 8:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f69b8c84308190b57d3b5b04bb4a78 |
completed | May 3, 2026, 12:49 a.m. |
Created at: April 9, 2026, 5:24 p.m.