Triple

T21246944
Position Surface form Disambiguated ID Type / Status
Subject Pleskov E523635 entity
Predicate refersTo P37 FINISHED
Object Pskov 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: Pskov | Statement: [Pleskov, refersTo, Pskov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pskov
Context triple: [Pleskov, refersTo, Pskov]
  • A. Pskov chosen
    Pskov is an ancient Russian city near the Estonian border, known for its medieval kremlin, historic churches, and role as a key fortress in northwestern Russia.
  • B. Yaroslavl
    Yaroslavl is a historic city in central Russia, located on the Volga River and known as one of the Golden Ring cities famed for its well-preserved medieval architecture and cultural heritage.
  • C. Kostroma
    Kostroma is a historic Russian city northeast of Moscow, known as part of the Golden Ring and for its well-preserved medieval architecture and monasteries.
  • D. 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.
  • E. Suzdal
    Suzdal is one of Russia’s oldest and best-preserved historic towns, renowned for its medieval churches, monasteries, and traditional wooden architecture.
  • 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_69e0b5146c108190adc9adb73e90abff completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7359abdac81908b74dad1b8cc0aa9 completed April 21, 2026, 8:30 a.m.
Created at: April 16, 2026, 3:54 p.m.