Triple
T23675630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сорочинці |
E584864
|
entity |
| Predicate | розташованеНаРічці |
P152946
|
FINISHED |
| Object | Псел |
—
|
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: Псел | Statement: [Сорочинці, розташованеНаРічці, Псел]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: розташованеНаРічці Context triple: [Сорочинці, розташованеНаРічці, Псел]
-
A.
посада
Indicates that one entity holds a specific official position, role, or office in relation to another entity (such as an organization or institution).
-
B.
successorInVolhynia
Indicates that one entity directly followed another in holding authority or position in Volhynia.
-
C.
outran
Indicates that one entity ran faster than another and moved ahead of them in a race or chase.
-
D.
UkrainianName
Indicates that an entity has a name that is in the Ukrainian language or follows Ukrainian naming conventions.
-
E.
plannedOnRiver
Indicates that something is intended or designed to be located, constructed, or carried out on or along a river.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:51 p.m.