Triple
T26298387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vuoksi basin |
E661479
|
entity |
| Predicate | hasOutletRiver |
P164201
|
FINISHED |
| Object | Vuoksi River |
—
|
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: Vuoksi River | Statement: [Vuoksi basin, hasOutletRiver, Vuoksi River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutletRiver Context triple: [Vuoksi basin, hasOutletRiver, Vuoksi River]
-
A.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
B.
hasRiverBelow
Indicates that one entity is located above another such that a river lies physically below it.
-
C.
hasRiverPortPotential
Indicates that a location has suitable conditions to support the development or operation of a river port.
-
D.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
-
E.
hasMajorTownOnRiver
Indicates that a major town is located on and directly associated with a particular 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f643c204508190a43fe0ec5165b01c |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 26, 2026, 10:13 p.m.