Triple

T9087183
Position Surface form Disambiguated ID Type / Status
Subject Hlukhiv E217787 entity
Predicate nearbyCity P350 FINISHED
Object Konotop E560093 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: Konotop | Statement: [Hlukhiv, nearbyCity, Konotop]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Konotop
Context triple: [Hlukhiv, nearbyCity, Konotop]
  • A. Konotop chosen
    Konotop is a historic city in northeastern Ukraine, known for the 1659 Battle of Konotop and its role as a regional railway and industrial center.
  • B. Horlivka
    Horlivka is an industrial city in eastern Ukraine’s Donetsk region, known for its coal mining and chemical industries and its location within the contested Donbas area.
  • C. Kostiantynivka
    Kostiantynivka is an industrial city in eastern Ukraine known for its metallurgical and glass production and its strategic location within Donetsk Oblast.
  • D. Kremenets
    Kremenets is a historic town in western Ukraine known for its rich cultural heritage and once-significant Jewish community.
  • E. Makiyivka
    Makiyivka is a major industrial city in eastern Ukraine’s Donetsk region, historically known for its coal mining and heavy industry.
  • 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_69ca83d8ab5881909d8fddae363b32b1 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc965646408190b041ab0e2d5dbc94 completed April 1, 2026, 3:51 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2817858008190b150417f9ef59b48 completed April 5, 2026, 3:36 p.m.
Created at: March 30, 2026, 7:13 p.m.