Triple
T22035989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romny |
E544209
|
entity |
| Predicate | administrativeCenterOf |
P383
|
FINISHED |
| Object | Romny 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: Romny Raion | Statement: [Romny, administrativeCenterOf, Romny Raion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Romny Raion Context triple: [Romny, administrativeCenterOf, Romny Raion]
-
A.
Romny Raion
chosen
Romny Raion is an administrative district in Sumy Oblast, northeastern Ukraine, centered around the city of Romny.
-
B.
Rivne Raion
Rivne Raion is an administrative district in Rivne Oblast in western Ukraine, encompassing the village of Velykyi Zhytyn among other localities.
-
C.
Nemyriv Raion
Nemyriv Raion was a former administrative district (raion) in Vinnytsia Oblast, central Ukraine, with the town of Nemyriv as its administrative center.
-
D.
Zolotonosha Raion
Zolotonosha Raion is an administrative district in Cherkasy Oblast, central Ukraine, centered around the city of Zolotonosha.
-
E.
Berezhany Raion
Berezhany Raion was a former administrative district in Ternopil Oblast, western Ukraine, centered around the town of Berezhany.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127f1f95c8190a324c84313cd91ee |
completed | April 28, 2026, 9:34 p.m. |
Created at: April 16, 2026, 8:25 p.m.