Triple

T4314346
Position Surface form Disambiguated ID Type / Status
Subject Mozhaysk Reservoir E94151 entity
Predicate locatedNear P294 FINISHED
Object Mozhaysk 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: Mozhaysk | Statement: [Mozhaysk Reservoir, locatedNear, Mozhaysk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mozhaysk
Context triple: [Mozhaysk Reservoir, locatedNear, Mozhaysk]
  • 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. Vsevolozhsk
    Vsevolozhsk is a town in northwestern Russia that serves as an important suburban and administrative center near Saint Petersburg.
  • C. Belozersk
    Belozersk is a historic town in northwestern Russia known for its medieval heritage and location near Lake Beloye.
  • 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. Kolomna
    Kolomna is a historic Russian city southeast of Moscow, known for its well-preserved kremlin, medieval architecture, and traditional pastila confectionery.
  • 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_69b3451886588190a3dd1305ea7c58dc completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b350f4448481908be2c7df9cc71bb9 completed March 12, 2026, 11:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69be396a2ff481908974870ceb903188 completed March 21, 2026, 6:23 a.m.
Created at: March 12, 2026, 11:12 p.m.