Triple
T9224976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ochakiv |
E221658
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Ochakiv Raion |
E219569
|
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: Ochakiv Raion | Statement: [Ochakiv, partOf, Ochakiv Raion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ochakiv Raion Context triple: [Ochakiv, partOf, Ochakiv Raion]
-
A.
Ochakiv Raion
chosen
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.
-
B.
Horokhiv Raion
Horokhiv Raion was a former administrative district in Volyn Oblast in northwestern Ukraine, centered around the town of Horokhiv.
-
C.
Kamin-Kashyrskyi Raion
Kamin-Kashyrskyi Raion is an administrative district in Volyn Oblast in northwestern Ukraine, known for its rural settlements and forested landscapes.
-
D.
Kropyvnytskyi Raion
Kropyvnytskyi Raion is an administrative district in central Ukraine’s Kirovohrad Oblast, centered around the city of Kropyvnytskyi.
-
E.
Hlukhiv Raion
Hlukhiv Raion was an administrative district in Sumy Oblast in northeastern Ukraine, centered around the historic city of Hlukhiv.
- 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_69ca83ec8db08190a9110df8232885d2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda9dbd1481909f35a4bee8e0b450 |
completed | April 1, 2026, 8:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d066521f288190a54b1199284db7a4 |
completed | April 4, 2026, 1:16 a.m. |
Created at: March 30, 2026, 7:28 p.m.