Triple
T13215108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vuoksi river basin |
E314590
|
entity |
| Predicate | hasPrimaryOutflowDirection |
P100480
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Vuoksi river basin, hasPrimaryOutflowDirection, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryOutflowDirection Context triple: [Vuoksi river basin, hasPrimaryOutflowDirection, south]
-
A.
hasPrimaryInflow
Indicates that one entity serves as the main source of inflowing material, energy, or influence into another entity.
-
B.
hasRunoffDirection
chosen
Indicates the direction in which runoff (such as water or other liquid) flows or is directed from a given source or surface.
-
C.
hasMajorOutflowBasin
Indicates that a geographic feature (such as a water body or watershed) has a specific basin into which most or all of its water ultimately flows.
-
D.
dataFlowDirection
Indicates the direction in which data moves or is transmitted from a source entity to a target entity.
-
E.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
- 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.