Triple
T8532285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nizhyn |
E201982
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Nizhyn Raion |
E727736
|
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: Nizhyn Raion | Statement: [Nizhyn, partOf, Nizhyn Raion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nizhyn Raion Context triple: [Nizhyn, partOf, Nizhyn Raion]
-
A.
Nizhyn Raion
chosen
Nizhyn Raion is an administrative district in Chernihiv Oblast in northern Ukraine, centered around the city of Nizhyn and encompassing several surrounding towns and rural communities.
-
B.
Chernihiv Raion
Chernihiv Raion is an administrative district in northern Ukraine that encompasses the city of Chernihiv and surrounding rural areas.
-
C.
Ternopil Raion
Ternopil Raion is an administrative district in Ternopil Oblast in western Ukraine, centered around the city of Ternopil.
-
D.
Poltava Raion
Poltava Raion is an administrative district in Poltava Oblast, central Ukraine, encompassing the city of Poltava and surrounding rural areas.
-
E.
Zhytomyr Raion
Zhytomyr Raion is an administrative district in Zhytomyr Oblast in northern Ukraine, encompassing the city of Zhytomyr 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe676e2ac8190b65a3d2a935776fd |
completed | March 31, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf280edb288190a7db5486cc426253 |
completed | April 3, 2026, 2:38 a.m. |
Created at: March 30, 2026, 6:17 p.m.