Triple

T9150204
Position Surface form Disambiguated ID Type / Status
Subject Horokhiv E219565 entity
Predicate administrativeCenterOf P383 FINISHED
Object Horokhiv Raion E781301 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: Horokhiv Raion | Statement: [Horokhiv, administrativeCenterOf, Horokhiv Raion]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horokhiv Raion
Context triple: [Horokhiv, administrativeCenterOf, Horokhiv Raion]
  • A. Horokhiv Raion chosen
    Horokhiv Raion was a former administrative district in Volyn Oblast in northwestern Ukraine, centered around the town of Horokhiv.
  • B. Hlukhiv Raion
    Hlukhiv Raion was an administrative district in Sumy Oblast in northeastern Ukraine, centered around the historic city of Hlukhiv.
  • C. Ochakiv Raion
    Ochakiv Raion is an administrative district in Mykolaiv Oblast in southern Ukraine, situated along the Black Sea coast and encompassing several coastal settlements and islands.
  • D. Kropyvnytskyi Raion
    Kropyvnytskyi Raion is an administrative district in central Ukraine’s Kirovohrad Oblast, centered around the city of Kropyvnytskyi.
  • E. Kamin-Kashyrskyi Raion
    Kamin-Kashyrskyi Raion is an administrative district in Volyn Oblast in northwestern Ukraine, known for its rural settlements and forested landscapes.
  • 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_69ca83e121dc81909912bd66953081c5 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca96908d88190a1d12517f6d1aece completed April 1, 2026, 5:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0545c5bb48190b889e6e9ef0448a5 completed April 3, 2026, 11:59 p.m.
Created at: March 30, 2026, 7:20 p.m.