Triple

T16697793
Position Surface form Disambiguated ID Type / Status
Subject Istra E405759 entity
Predicate roadDistanceTo P7750 FINISHED
Object Zvenigorod 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: Zvenigorod | Statement: [Istra, roadDistanceTo, Zvenigorod]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zvenigorod
Context triple: [Istra, roadDistanceTo, Zvenigorod]
  • A. Zvenigorod chosen
    Zvenigorod is a historic town near Moscow, Russia, known for its ancient monasteries, traditional Russian architecture, and role as a cultural and spiritual center.
  • B. Ivangorod
    Ivangorod is a Russian border town on the Narva River, known for its medieval fortress facing the Estonian city of Narva.
  • C. Volodarsk
    Volodarsk is a town in Nizhny Novgorod Oblast, Russia, known for its location along the Klyazma River and its industrial character.
  • D. Gorodets
    Gorodets is an ancient Russian town on the Volga River, known as one of the oldest settlements in the Nizhny Novgorod region and historically significant as a medieval trading and craft center.
  • E. Priozersk
    Priozersk is a small town in northwestern Russia known for its historic fortress Korela and its location on the shores of Lake Ladoga.
  • 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_69d8838db21081909589220fd71440a4 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3832e93c48190a594c498e9cc901a completed April 18, 2026, 1:12 p.m.
Created at: April 10, 2026, 5:19 a.m.