Triple
T11985719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pechora Railway |
E285272
|
entity |
| Predicate | terminus |
P388
|
FINISHED |
| Object | Vorkuta |
E282195
|
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: Vorkuta | Statement: [Pechora Railway, terminus, Vorkuta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vorkuta Context triple: [Pechora Railway, terminus, Vorkuta]
-
A.
Vorkuta
chosen
Vorkuta is a remote Arctic city in Russia historically known as one of the largest centers of the Soviet Gulag labor camp system.
-
B.
Apatity
Apatity is an industrial and scientific town in Russia’s Murmansk Oblast, known for its phosphate mining and research institutes within the Arctic Kola Peninsula region.
-
C.
Degtyarsk
Degtyarsk is a small industrial town in Russia’s Sverdlovsk Oblast, historically known for its mining activities.
-
D.
Odintsovo
Odintsovo is a town in western Russia that serves as an important suburban center just outside Moscow.
-
E.
Salekhard
Salekhard is a Russian Arctic city located on the Ob River and notable as the only city in the world situated directly on the Arctic Circle.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f63e99d88190b718217005464954 |
completed | May 2, 2026, 1:03 p.m. |
Created at: April 8, 2026, 9:46 p.m.