Triple

T14808013
Position Surface form Disambiguated ID Type / Status
Subject Pereyaslavl line E348090 entity
Predicate hasTerritorialBase P21614 FINISHED
Object Pereyaslavl E307009 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: Pereyaslavl | Statement: [Pereyaslavl line, hasTerritorialBase, Pereyaslavl]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pereyaslavl
Context triple: [Pereyaslavl line, hasTerritorialBase, 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 (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_69d822ea8b7c819097dfadf3d45545e6 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69decf33b6a08190ab6a4cfeda2cc09c completed April 14, 2026, 11:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff0b3216fc8190b79740a993b98cb3 completed May 9, 2026, 10:23 a.m.
Created at: April 10, 2026, 1:44 a.m.