Triple

T9080834
Position Surface form Disambiguated ID Type / Status
Subject Cherepovets E217616 entity
Predicate distanceTo P350 FINISHED
Object Vologda E452953 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: Vologda | Statement: [Cherepovets, distanceTo, Vologda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vologda
Context triple: [Cherepovets, distanceTo, Vologda]
  • A. Vologda chosen
    Vologda is a historic city in northwestern Russia known for its well-preserved wooden architecture, ancient monasteries, and traditional lace-making.
  • B. Volokolamsk
    Volokolamsk is a historic town in western Russia, located northwest of Moscow and known for its medieval origins and role in regional trade and defense.
  • C. Vologda Oblast
    Vologda Oblast is a federal subject of Russia known for its historic cities, traditional wooden architecture, and significant timber and metallurgy industries in the country’s northwest.
  • D. Kostroma
    Kostroma is a historic Russian city northeast of Moscow, known as part of the Golden Ring and for its well-preserved medieval architecture and monasteries.
  • E. Ivangorod
    Ivangorod is a Russian border town on the Narva River, known for its medieval fortress facing the Estonian city of Narva.
  • 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_69ca83d7a0388190ba1af89ed7ba36f9 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc9607942c8190a21620892ce3cbe5 completed April 1, 2026, 3:50 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1eaa8135081909225810ee5355bc3 completed April 5, 2026, 4:52 a.m.
Created at: March 30, 2026, 7:13 p.m.