Triple

T22480695
Position Surface form Disambiguated ID Type / Status
Subject Rowno E555755 entity
Predicate isAdministrativeCenterOf P1474 FINISHED
Object Rivne 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: Rivne Raion | Statement: [Rowno, isAdministrativeCenterOf, Rivne Raion]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rivne Raion
Context triple: [Rowno, isAdministrativeCenterOf, Rivne Raion]
  • A. Rivne Raion chosen
    Rivne Raion is an administrative district in Rivne Oblast in western Ukraine, encompassing the village of Velykyi Zhytyn among other localities.
  • B. Nizhyn Raion
    Nizhyn Raion is an administrative district in Chernihiv Oblast in northern Ukraine, centered around the city of Nizhyn and encompassing several surrounding towns and rural communities.
  • C. Chernihiv Raion
    Chernihiv Raion is an administrative district in northern Ukraine that encompasses the city of Chernihiv and surrounding rural areas.
  • D. Poltava Raion
    Poltava Raion is an administrative district in Poltava Oblast, central Ukraine, encompassing the city of Poltava and surrounding rural areas.
  • E. Ternopil Raion
    Ternopil Raion is an administrative district in Ternopil Oblast in western Ukraine, centered around the city of Ternopil.
  • 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_69e11e53897c819088863779f8c50bb0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15c3836a08190b6f0d88b94cb80a3 completed April 29, 2026, 1:17 a.m.
Created at: April 16, 2026, 8:49 p.m.