Triple
T19270984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yahotyn |
E481921
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Boryspil 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: Boryspil Raion | Statement: [Yahotyn, partOf, Boryspil Raion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Boryspil Raion Context triple: [Yahotyn, partOf, Boryspil Raion]
-
A.
Boryspil Raion
chosen
Boryspil Raion is an administrative district in Kyiv Oblast, Ukraine, known for encompassing the city that hosts the country’s main international airport.
-
B.
Kyiv-Sviatoshyn Raion
Kyiv-Sviatoshyn Raion was a former administrative district in Kyiv Oblast, Ukraine, that encompassed several suburban settlements surrounding the capital.
-
C.
Dnipro Raion
Dnipro Raion is an administrative district in Dnipropetrovsk Oblast, Ukraine, centered around the city of Dnipro.
-
D.
Hlukhiv Raion
Hlukhiv Raion was an administrative district in Sumy Oblast in northeastern Ukraine, centered around the historic city of Hlukhiv.
-
E.
Bucha Raion
Bucha Raion is an administrative district in Kyiv Oblast, Ukraine, encompassing several towns and settlements on the outskirts of the capital.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbb8bea08190b5c65eebe67dccbb |
completed | April 20, 2026, 10:11 a.m. |
Created at: April 10, 2026, 1:29 p.m.