Triple
T18712901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaroslavsky railway line |
E457560
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Khotkovo |
—
|
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: Khotkovo | Statement: [Yaroslavsky railway line, serves, Khotkovo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khotkovo Context triple: [Yaroslavsky railway line, serves, Khotkovo]
-
A.
Khotkovo
chosen
Khotkovo is a small Russian town in Moscow Oblast known for its historical churches and proximity to the famous Trinity Lavra of St. Sergius.
-
B.
Ostashkov
Ostashkov is a historic town in western Russia situated on the shores of Lake Seliger, known as a local tourist and pilgrimage center.
-
C.
Aksakovo
Aksakovo is a town in northeastern Bulgaria that serves as an important residential and industrial center near the city of Varna.
-
D.
Zayukovo
Zayukovo is a rural locality in the Kabardino-Balkar Republic of Russia situated along the Baksan River in the North Caucasus region.
-
E.
Kovylkino
Kovylkino is a small town in the Republic of Mordovia, Russia, known as a local industrial and transportation 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56ab352b481909b444e7c476898f4 |
completed | April 19, 2026, 11:52 p.m. |
Created at: April 10, 2026, 11:50 a.m.