Triple

T11207713
Position Surface form Disambiguated ID Type / Status
Subject Narva River E265214 entity
Predicate cityOnRiver P165 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: [Narva River, cityOnRiver, Ivangorod]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ivangorod
Context triple: [Narva River, cityOnRiver, 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. Zvenigorod
    Zvenigorod is a historic town near Moscow, Russia, known for its ancient monasteries, traditional Russian architecture, and role as a cultural and spiritual center.
  • E. Zaraysk
    Zaraysk is a historic town in Moscow Oblast, Russia, known for its well-preserved medieval kremlin and role as a former regional administrative center.
  • 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_69d6aac59460819089b9848b27f57848 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8d5f8908190903817f84c629ba1 completed April 9, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69f470cbce14819099d47d468ae61df7 completed May 1, 2026, 9:22 a.m.
Created at: April 8, 2026, 9:30 p.m.