Triple

T14001137
Position Surface form Disambiguated ID Type / Status
Subject Lozova E336826 entity
Predicate administrativeCenterOf P383 FINISHED
Object Lozova Raion E1073734 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: Lozova Raion | Statement: [Lozova, administrativeCenterOf, Lozova Raion]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lozova Raion
Context triple: [Lozova, administrativeCenterOf, Lozova Raion]
  • A. Lozova Raion chosen
    Lozova Raion is an administrative district in Kharkiv Oblast, Ukraine, centered around the city of Lozova.
  • 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. Shatsk Raion
    Shatsk Raion was a former administrative district in Volyn Oblast, northwestern Ukraine, known for encompassing the Shatsk Lakes region near the borders with Poland and Belarus.
  • D. Dzhankoi Raion
    Dzhankoi Raion is an administrative district in the northern part of Crimea, centered around the town of Dzhankoi.
  • E. Ratne Raion
    Ratne Raion is a former administrative district in Volyn Oblast in northwestern Ukraine, known for encompassing the urban-type settlement of Ratne and surrounding rural areas.
  • 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_69d81c645c5c8190b1fd16a285a1b78a completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2ed06a50819093ddc64f55050689 completed April 14, 2026, 12:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69fbc329891c8190b4dcb9913e235a1c completed May 6, 2026, 10:39 p.m.
Created at: April 9, 2026, 10:19 p.m.