Triple
T26298362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vuoksi basin |
E661479
|
entity |
| Predicate | basinSovereignCountry |
P411
|
FINISHED |
| Object | Finland |
—
|
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: Finland | Statement: [Vuoksi basin, basinSovereignCountry, Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basinSovereignCountry Context triple: [Vuoksi basin, basinSovereignCountry, Finland]
-
A.
basinCountry
chosen
Indicates the country or countries within whose territory a river basin or drainage area is primarily located or through which it significantly extends.
-
B.
basinPartOf
Indicates that one basin is a component or subdivision of a larger basin or basin system.
-
C.
reservoirCountry
Indicates that a country contains or hosts the reservoir associated with the referenced entity.
-
D.
countryDownstreamBasin
Indicates that one country lies within the downstream portion of a river basin relative to another country or reference point.
-
E.
basinProvince
Indicates a relationship where a geological basin is located within, associated with, or governed by a particular province or administrative region.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60eb080b08190a45b05aa6d6219e9 |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:13 p.m.