Triple

T5443821
Position Surface form Disambiguated ID Type / Status
Subject European route E20 E122198 entity
Predicate passesThrough P225 FINISHED
Object Ivangorod E458157 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: Ivangorod | Statement: [European route E20, passesThrough, Ivangorod]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ivangorod
Context triple: [European route E20, passesThrough, Ivangorod]
  • A. Ivangorod chosen
    Ivangorod is a Russian border town on the Narva River, known for its medieval fortress facing the Estonian city of Narva.
  • B. Pereiaslavl
    Pereiaslavl was one of the principal urban centers of Kyivan Rus, serving as an important political, military, and cultural hub in medieval Eastern Europe.
  • C. Votkinsk
    Votkinsk is a Russian town in Udmurtia best known as the birthplace of composer Pyotr Ilyich Tchaikovsky.
  • D. Torzhok
    Torzhok is a historic town in western Russia known for its medieval architecture, traditional goldwork embroidery, and location on the Tvertsa River.
  • E. Vsevolozhsk
    Vsevolozhsk is a town in northwestern Russia that serves as an important suburban and administrative center near Saint Petersburg.
  • 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_69bd4640f52c81909e653ec361f66d76 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd91ccdd648190940c04781c4222ec completed March 20, 2026, 6:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69c11331275c8190950247127d8e33c6 completed March 23, 2026, 10:17 a.m.
Created at: March 20, 2026, 2:07 p.m.