Triple
T20093737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pavlohrad |
E496341
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Pavlohrad 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: Pavlohrad Raion | Statement: [Pavlohrad, partOf, Pavlohrad Raion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pavlohrad Raion Context triple: [Pavlohrad, partOf, Pavlohrad Raion]
-
A.
Pavlohrad Raion
chosen
Pavlohrad Raion is an administrative district in Dnipropetrovsk Oblast, Ukraine, centered around the city of Pavlohrad.
-
B.
Vyshhorod Raion
Vyshhorod Raion is an administrative district in Kyiv Oblast, Ukraine, encompassing the town of Vyshhorod and surrounding settlements north of Kyiv.
-
C.
Chervonohrad Raion
Chervonohrad Raion is an administrative district in Lviv Oblast, western Ukraine, that includes the town of Sokal among its settlements.
-
D.
Horokhiv Raion
Horokhiv Raion was a former administrative district in Volyn Oblast in northwestern Ukraine, centered around the town of Horokhiv.
-
E.
Snihurivka Raion
Snihurivka Raion was a former administrative district in Mykolaiv Oblast, Ukraine, centered around the town of Snihurivka.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666a7a94819080ebabfba9762f97 |
completed | April 20, 2026, 5:46 p.m. |
Created at: April 11, 2026, 11:23 p.m.