Triple
T17768990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lubny |
E443583
|
entity |
| Predicate | administrativeCenterOf |
P383
|
FINISHED |
| Object | Lubny 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: Lubny Raion | Statement: [Lubny, administrativeCenterOf, Lubny Raion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lubny Raion Context triple: [Lubny, administrativeCenterOf, Lubny Raion]
-
A.
Lubny Raion
chosen
Lubny Raion is an administrative district in Poltava Oblast, central Ukraine, centered around the city of Lubny.
-
B.
Berezhany Raion
Berezhany Raion was a former administrative district in Ternopil Oblast, western Ukraine, centered around the town of Berezhany.
-
C.
Kropyvnytskyi Raion
Kropyvnytskyi Raion is an administrative district in central Ukraine’s Kirovohrad Oblast, centered around the city of Kropyvnytskyi.
-
D.
Poltava Raion
Poltava Raion is an administrative district in Poltava Oblast, central Ukraine, encompassing the city of Poltava and surrounding rural areas.
-
E.
Nemyriv Raion
Nemyriv Raion was a former administrative district (raion) in Vinnytsia Oblast, central Ukraine, with the town of Nemyriv as its administrative center.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fe70648190b4107e1eabacc694 |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 10:11 a.m.