Triple
T14896676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhine–Danube watershed |
E359893
|
entity |
| Predicate | drainageDirectionOnRhineSide |
P8846
|
FINISHED |
| Object | northwest toward North Sea |
—
|
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: northwest toward North Sea | Statement: [Rhine–Danube watershed, drainageDirectionOnRhineSide, northwest toward North Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainageDirectionOnRhineSide Context triple: [Rhine–Danube watershed, drainageDirectionOnRhineSide, northwest toward North Sea]
-
A.
drainageDirection
chosen
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
B.
isMainRhineBranchInNetherlands
Indicates that a river segment is the principal branch of the Rhine within the territory of the Netherlands.
-
C.
waterwayDirection
Indicates the directional flow or orientation of a waterway relative to a reference point or path.
-
D.
hasCityOnRightBank
Indicates that a city is located on the right bank of a specified river or watercourse.
-
E.
directionFromBern
Indicates the cardinal or relative direction in which one entity is located when measured outward starting from Bern.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded6070b248190be8f4f91a0c0b1f3 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:11 a.m.