Triple

T14936106
Position Surface form Disambiguated ID Type / Status
Subject Central sector of the Eastern Front E372394 entity
Predicate notableCity P2813 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: [Central sector of the Eastern Front, notableCity, Smolensk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Smolensk
Context triple: [Central sector of the Eastern Front, notableCity, 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. Smolenskaya
    Smolenskaya is a Moscow Metro station on the Arbatsko–Pokrovskaya and Filyovskaya lines, located near the historic Arbat district.
  • D. Borisoglebsk
    Borisoglebsk is a small Russian city known for its historical architecture and location on the Vorona River in southwestern Russia.
  • E. 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.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded647ae388190a0e97c03f2a4d832 completed April 15, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff908410548190ada5d4f71d52919b completed May 9, 2026, 7:52 p.m.
Created at: April 10, 2026, 2:37 a.m.