Triple

T15894404
Position Surface form Disambiguated ID Type / Status
Subject Pavlograd E385414 entity
Predicate administrativeCenterOf P383 FINISHED
Object Pavlohrad Raion E1182838 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: Pavlohrad Raion | Statement: [Pavlograd, administrativeCenterOf, Pavlohrad Raion]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pavlohrad Raion
Context triple: [Pavlograd, administrativeCenterOf, Pavlohrad Raion]
  • A. Pavlohrad Raion chosen
    Pavlohrad Raion is an administrative district in Dnipropetrovsk Oblast, Ukraine, centered around the city of Pavlohrad.
  • B. Chervonohrad Raion
    Chervonohrad Raion is an administrative district in Lviv Oblast, western Ukraine, that includes the town of Sokal among its settlements.
  • C. Horokhiv Raion
    Horokhiv Raion was a former administrative district in Volyn Oblast in northwestern Ukraine, centered around the town of Horokhiv.
  • D. Nemyriv Raion
    Nemyriv Raion was a former administrative district (raion) in Vinnytsia Oblast, central Ukraine, with the town of Nemyriv as its administrative center.
  • E. Kropyvnytskyi Raion
    Kropyvnytskyi Raion is an administrative district in central Ukraine’s Kirovohrad Oblast, centered around the city of Kropyvnytskyi.
  • 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_69d86da5b800819083a31be937d738b0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1563809748190a54156b946d3f061 completed April 16, 2026, 9:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffb5a1b1548190a8579cebf9e71121 completed May 9, 2026, 10:30 p.m.
Created at: April 10, 2026, 4:51 a.m.