Triple

T11195578
Position Surface form Disambiguated ID Type / Status
Subject Smolensk War E264912 entity
Predicate location P40 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 War, location, Smolensk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Smolensk
Context triple: [Smolensk War, location, 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. Borisoglebsk
    Borisoglebsk is a small Russian city known for its historical architecture and location on the Vorona River in southwestern Russia.
  • 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. 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.
  • 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_69d6aa9eb9248190b20211772621b4bc completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8bf14e481908563b15790af4d20 completed April 9, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69e509dd91288190beefaaa451d692ae completed April 19, 2026, 4:59 p.m.
Created at: April 8, 2026, 9:29 p.m.