Triple

T13454064
Position Surface form Disambiguated ID Type / Status
Subject Enisei E311182 entity
Predicate majorCityOnRiver P316 FINISHED
Object Divnogorsk E318919 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: Divnogorsk | Statement: [Enisei, majorCityOnRiver, Divnogorsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Divnogorsk
Context triple: [Enisei, majorCityOnRiver, Divnogorsk]
  • A. Divnogorsk chosen
    Divnogorsk is a small Siberian town in Krasnoyarsk Krai, Russia, known for its location in the Yenisei River valley and its association with the Krasnoyarsk hydroelectric power station.
  • B. Yalutorovsk
    Yalutorovsk is a historic town in western Siberia, Russia, known for its 17th-century origins as a fortress settlement and its location on the Tobol River.
  • C. Krasnogorsk
    Krasnogorsk is a city in western Russia that serves as an important administrative and residential center just outside Moscow.
  • D. Petrovskoye
    Petrovskoye was the original Russian fortress settlement that later developed into the modern city of Makhachkala in Dagestan, Russia.
  • E. Novouralsk
    Novouralsk is a closed industrial city in Russia known historically for its role in the Soviet and Russian nuclear industry, particularly uranium enrichment.
  • 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_69d806a938b8819097ec43a2229fc7f9 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaefc52448190b30d7999f44a9765 completed April 12, 2026, 2:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7c0d591648190beb4430c6b199eb8 completed May 3, 2026, 9:40 p.m.
Created at: April 9, 2026, 9:41 p.m.