Triple
T17768989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lubny |
E443583
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object |
Lubny Raion
Lubny Raion is an administrative district in Poltava Oblast, central Ukraine, centered around the city of Lubny.
|
E1302484
|
NE FINISHED |
How this triple was built (4 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, partOf, Lubny Raion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lubny Raion Context triple: [Lubny, partOf, Lubny Raion]
-
A.
Berezhany Raion
Berezhany Raion was a former administrative district in Ternopil Oblast, western Ukraine, centered around the town of Berezhany.
-
B.
Kropyvnytskyi Raion
Kropyvnytskyi Raion is an administrative district in central Ukraine’s Kirovohrad Oblast, centered around the city of Kropyvnytskyi.
-
C.
Poltava Raion
Poltava Raion is an administrative district in Poltava Oblast, central Ukraine, encompassing the city of Poltava and surrounding rural areas.
-
D.
Nemyriv Raion
Nemyriv Raion was a former administrative district (raion) in Vinnytsia Oblast, central Ukraine, with the town of Nemyriv as its administrative center.
-
E.
Kamin-Kashyrskyi Raion
Kamin-Kashyrskyi Raion is an administrative district in Volyn Oblast in northwestern Ukraine, known for its rural settlements and forested landscapes.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Lubny Raion Triple: [Lubny, partOf, Lubny Raion]
Generated description
Lubny Raion is an administrative district in Poltava Oblast, central Ukraine, centered around the city of Lubny.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Lubny Raion Target entity description: Lubny Raion is an administrative district in Poltava Oblast, central Ukraine, centered around the city of Lubny.
-
A.
Berezhany Raion
Berezhany Raion was a former administrative district in Ternopil Oblast, western Ukraine, centered around the town of Berezhany.
-
B.
Kropyvnytskyi Raion
Kropyvnytskyi Raion is an administrative district in central Ukraine’s Kirovohrad Oblast, centered around the city of Kropyvnytskyi.
-
C.
Poltava Raion
Poltava Raion is an administrative district in Poltava Oblast, central Ukraine, encompassing the city of Poltava and surrounding rural areas.
-
D.
Nemyriv Raion
Nemyriv Raion was a former administrative district (raion) in Vinnytsia Oblast, central Ukraine, with the town of Nemyriv as its administrative center.
-
E.
Kamin-Kashyrskyi Raion
Kamin-Kashyrskyi Raion is an administrative district in Volyn Oblast in northwestern Ukraine, known for its rural settlements and forested landscapes.
- F. None of above. chosen
Provenance (5 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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a034998e08081909bb8b9711002486f |
completed | May 12, 2026, 3:39 p.m. |
| NEDg | Description generation | batch_6a034b0817408190817e4a3ee0003d57 |
completed | May 12, 2026, 3:45 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a034bdf5c808190ac329e663e220f1b |
completed | May 12, 2026, 3:48 p.m. |
Created at: April 10, 2026, 10:11 a.m.