Triple

T4055795
Position Surface form Disambiguated ID Type / Status
Subject Smolensk–Moscow Upland E84689 entity
Predicate nearCity P350 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: [Smolensk–Moscow Upland, nearCity, Smolensk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Smolensk
Context triple: [Smolensk–Moscow Upland, nearCity, 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. Kaluga
    Kaluga is a historic city in western Russia known as a regional administrative center and an important site in several Russian uprisings and military campaigns.
  • 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_69aed933bec881909edfa28ebb69c634 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefbabec608190a35d39d3d03b928b completed March 9, 2026, 4:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69badb16faf88190aa047ba701ff7c0d completed March 18, 2026, 5:04 p.m.
Created at: March 9, 2026, 3:38 p.m.