Triple
T19531201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E22 European route |
E488655
|
entity |
| Predicate | passesThrough |
P225
|
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: [E22 European route, passesThrough, Velikiye Luki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Velikiye Luki Context triple: [E22 European route, passesThrough, 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.
Ulyanovskoye
Ulyanovskoye is a settlement located along the Sviyaga River in Russia.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363ec6cc8190b9e9ac0196b288f9 |
completed | April 20, 2026, 2:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0771a1ebac819090982f36b4c02446 |
completed | May 15, 2026, 7:18 p.m. |
Created at: April 10, 2026, 1:41 p.m.