Triple

T18078388
Position Surface form Disambiguated ID Type / Status
Subject Shepetivka E432618 entity
Predicate regionCapitalOf P204 FINISHED
Object Shepetivka Raion NE NERFINISHED

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: Shepetivka Raion | Statement: [Shepetivka, regionCapitalOf, Shepetivka Raion]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shepetivka Raion
Context triple: [Shepetivka, regionCapitalOf, Shepetivka Raion]
  • A. Shepetivka Raion chosen
    Shepetivka Raion is an administrative district in Khmelnytskyi Oblast in western Ukraine, centered around the town of Shepetivka.
  • B. Nemyriv Raion
    Nemyriv Raion was a former administrative district (raion) in Vinnytsia Oblast, central Ukraine, with the town of Nemyriv as its administrative center.
  • C. Horokhiv Raion
    Horokhiv Raion was a former administrative district in Volyn Oblast in northwestern Ukraine, centered around the town of Horokhiv.
  • D. Rakhiv Raion
    Rakhiv Raion is an administrative district in Zakarpattia Oblast in western Ukraine, known for its mountainous terrain in the Carpathians and proximity to the country’s geographic center.
  • E. Volodymyr Raion
    Volodymyr Raion is an administrative district in Volyn Oblast in western Ukraine, centered around the city of Volodymyr.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9070cac81909fa9473fb1c3f1c7 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4d9f6a85481909894c39c8be98d5d completed April 19, 2026, 1:34 p.m.
Created at: April 10, 2026, 10:27 a.m.