Triple

T6868352
Position Surface form Disambiguated ID Type / Status
Subject Rus' E158473 entity
Predicate majorCity P316 FINISHED
Object Smolensk E134449 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: Smolensk | Statement: [Rus', majorCity, Smolensk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Smolensk
Context triple: [Rus', majorCity, Smolensk]
  • A. Smolensk chosen
    Smolensk is a historic city in western Russia near the Belarusian border, known for its strategic location and centuries-old fortifications.
  • B. Podolsk
    Podolsk is a major industrial city and former center of machine-building located just south of Moscow in western Russia.
  • C. 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.
  • D. 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.
  • E. Pskov
    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.
  • 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_69c68831e3648190a643c328122e4d43 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d8a793a481909340239c065393a4 completed March 27, 2026, 7:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8274d1994819089af156d634547ee completed March 28, 2026, 7:09 p.m.
Created at: March 27, 2026, 2:21 p.m.