Triple

T3397314
Position Surface form Disambiguated ID Type / Status
Subject Mozhaisk defensive line E71559 entity
Predicate near P350 FINISHED
Object Mozhaisk E393129 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: Mozhaisk | Statement: [Mozhaisk defensive line, near, Mozhaisk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mozhaisk
Context triple: [Mozhaisk defensive line, near, Mozhaisk]
  • A. Mozhaisk chosen
    Mozhaisk is a historic town in Moscow Oblast, Russia, known for its strategic military importance as a western defensive outpost for Moscow and its notable architectural and cultural heritage.
  • B. Kolomna
    Kolomna is a historic Russian city southeast of Moscow, known for its well-preserved kremlin, medieval architecture, and traditional pastila confectionery.
  • C. Terekhovo
    Terekhovo is a metro station on Moscow’s Big Circle Line, serving the Terekhovo area in the western part of the city.
  • D. Belozersk
    Belozersk is a historic town in northwestern Russia known for its medieval heritage and location near Lake Beloye.
  • E. Torzhok
    Torzhok is a historic town in western Russia known for its medieval architecture, traditional goldwork embroidery, and location on the Tvertsa River.
  • 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_69ad85a9c4a88190a854019341cb3b60 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb8c4099081908a236376b4f86900 completed March 8, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69b511ff137c8190bf9ca22dd71bd205 completed March 14, 2026, 7:45 a.m.
Created at: March 8, 2026, 3:14 p.m.