Triple
T18859355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drammensfjord |
E461266
|
entity |
| Predicate | drainsBasin |
P1559
|
FINISHED |
| Object | Drammenselva watershed |
—
|
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: Drammenselva watershed | Statement: [Drammensfjord, drainsBasin, Drammenselva watershed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainsBasin Context triple: [Drammensfjord, drainsBasin, Drammenselva watershed]
-
A.
drainageBasin
chosen
Indicates the area of land where all precipitation and surface water flow are collected and drained toward a particular river, lake, or other water body.
-
B.
drainageBasinOnOtherSide
Indicates that the drainage basin associated with one entity lies on the opposite side of a dividing feature (such as a watershed or boundary) from the drainage basin associated with another entity.
-
C.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
-
D.
resourceBasin
Indicates a relationship where a basin serves as a source or reservoir of resources for another entity or area.
-
E.
drainsInto
Indicates that one entity serves as a source or conduit whose contents or flow are directed into 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c05fb800819098951ec134a1fa2a |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.