Triple
T22474650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lokhvytsia |
E555596
|
entity |
| Predicate | administrativeCenterOf |
P383
|
FINISHED |
| Object | Lokhvytsia 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: Lokhvytsia Raion | Statement: [Lokhvytsia, administrativeCenterOf, Lokhvytsia Raion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lokhvytsia Raion Context triple: [Lokhvytsia, administrativeCenterOf, Lokhvytsia Raion]
-
A.
Lokhvytsia Raion
chosen
Lokhvytsia Raion was an administrative district (raion) in Poltava Oblast, central Ukraine, centered around the town of Lokhvytsia.
-
B.
Berezhany Raion
Berezhany Raion was a former administrative district in Ternopil Oblast, western Ukraine, centered around the town of Berezhany.
-
C.
Poltava Raion
Poltava Raion is an administrative district in Poltava Oblast, central Ukraine, encompassing the city of Poltava and surrounding rural areas.
-
D.
Horodnia Raion
Horodnia Raion was a former administrative district in Chernihiv Oblast in northern Ukraine, centered around the town of Horodnia.
-
E.
Zolotonosha Raion
Zolotonosha Raion is an administrative district in Cherkasy Oblast, central Ukraine, centered around the city of Zolotonosha.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be2d5388190a59d11b3403d998b |
completed | April 29, 2026, 1:16 a.m. |
Created at: April 16, 2026, 8:49 p.m.