Triple
T13215116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vuoksi river basin |
E314590
|
entity |
| Predicate | transboundaryWaterSystem |
P66357
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Vuoksi river basin, transboundaryWaterSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transboundaryWaterSystem Context triple: [Vuoksi river basin, transboundaryWaterSystem, true]
-
A.
transboundaryBasin
chosen
Indicates that a river basin or watershed extends across and is shared by the territories of two or more political or administrative jurisdictions.
-
B.
transboundaryRiverOf
Indicates that a river crosses or forms the boundary between two or more political or administrative regions.
-
C.
transboundaryWaterManagement
Indicates the cooperative planning, regulation, and use of shared water resources that cross political or administrative boundaries between different jurisdictions.
-
D.
tributarySystem
Indicates a relationship where one political entity pays regular tribute or offers deference to another, acknowledging the latter’s superior authority or status.
-
E.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf28c9c819080d7b42d20f579d1 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:18 p.m.