Triple

T11276559
Position Surface form Disambiguated ID Type / Status
Subject Ivankovo Hydroelectric Station E266951 entity
Predicate locatedNear P294 FINISHED
Object Konakovo E332297 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: Konakovo | Statement: [Ivankovo Hydroelectric Station, locatedNear, Konakovo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Konakovo
Context triple: [Ivankovo Hydroelectric Station, locatedNear, Konakovo]
  • A. Konakovo chosen
    Konakovo is a town in Tver Oblast, Russia, situated on the Volga River and known for its power station and riverside recreation.
  • B. Kuvshinovo
    Kuvshinovo is a small town in Tver Oblast, Russia, known primarily as a local industrial and administrative center.
  • C. Makeyevka
    Makeyevka is an industrial city in eastern Ukraine’s Donetsk Oblast, historically known for its coal mining and metallurgical industries.
  • D. Aksakovo
    Aksakovo is a town in northeastern Bulgaria that serves as an important residential and industrial center near the city of Varna.
  • E. Petrovskoye
    Petrovskoye was the original Russian fortress settlement that later developed into the modern city of Makhachkala in Dagestan, Russia.
  • 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_69d6aac8c2f48190ad0596f1f89f0470 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e966cb4c8190bc410d7e623e54db completed April 9, 2026, 6:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4f455f0bc8190994c57264f775f60 completed April 19, 2026, 3:27 p.m.
Created at: April 8, 2026, 9:31 p.m.