Triple

T20768034
Position Surface form Disambiguated ID Type / Status
Subject Yaropolk II of Kiev E511150 entity
Predicate territorialControl P647 FINISHED
Object Pereyaslavl 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: Pereyaslavl | Statement: [Yaropolk II of Kiev, territorialControl, Pereyaslavl]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pereyaslavl
Context triple: [Yaropolk II of Kiev, territorialControl, Pereyaslavl]
  • A. Pereiaslavl chosen
    Pereiaslavl was one of the principal urban centers of Kyivan Rus, serving as an important political, military, and cultural hub in medieval Eastern Europe.
  • B. Yuryev-Polsky
    Yuryev-Polsky is a historic small town in central Russia known for its ancient white-stone churches and traditional Russian architecture.
  • C. Pleskov
    Pleskov is an alternative historical or variant name for the Russian city of Pskov, a historic regional center in northwestern Russia.
  • D. Ivangorod
    Ivangorod is a Russian border town on the Narva River, known for its medieval fortress facing the Estonian city of Narva.
  • 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 (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_69e0b4ca01148190ac018e57e0cab46f completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c24df58c8190b37398353ce4bf24 completed April 21, 2026, 12:18 a.m.
Created at: April 16, 2026, 12:36 p.m.