Triple
T10429594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarpsfossen |
E245873
|
entity |
| Predicate | watercourseRegulatedBy |
P68423
|
FINISHED |
| Object | hydropower dams |
—
|
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: hydropower dams | Statement: [Sarpsfossen, watercourseRegulatedBy, hydropower dams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseRegulatedBy Context triple: [Sarpsfossen, watercourseRegulatedBy, hydropower dams]
-
A.
watercourseControlled
chosen
Indicates that one entity exercises control, regulation, or management over a watercourse (such as a river, stream, or canal).
-
B.
waterManagementArea
Indicates the designated region or zone over which specific water resources are managed, regulated, or administered.
-
C.
inflowWatercourse
Indicates that one watercourse flows into or feeds another water body or watercourse.
-
D.
watercourseId
Indicates the identifier that uniquely associates an entity with a specific watercourse (such as a river, stream, or canal).
-
E.
waterwayMaintainedBy
Indicates that a particular waterway is maintained, managed, or serviced by a specified agent or organization.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea4b4b5881908ae23f8efeea482b |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:13 p.m.