Triple
T23675656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сорочинці |
E584864
|
entity |
| Predicate | географічнийРегіон |
P64798
|
FINISHED |
| Object | Лівобережна Україна |
—
|
LITERAL 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: Лівобережна Україна | Statement: [Сорочинці, географічнийРегіон, Лівобережна Україна]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: географічнийРегіон Context triple: [Сорочинці, географічнийРегіон, Лівобережна Україна]
-
A.
geographicalRegionType
Indicates the specific kind or category of geographical region that an entity belongs to (e.g., continent, country, province, or city).
-
B.
geopoliticalRegion
Indicates a relationship where an entity is a defined political or administrative geographic area, such as a country, state, province, or similar region.
-
C.
placeRegion
chosen
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
D.
geographicDivision
Indicates that one place is an administrative or territorial subdivision of another place.
-
E.
longitudeRegion
Indicates that an entity is located within or associated with a specific longitudinal region on the Earth’s surface.
- F. None of above.
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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f2e35c8190ada29694e2cbed37 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.