Triple
T4365714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drammenselva |
E98765
|
entity |
| Predicate | watercourseId |
P55797
|
FINISHED |
| Object | 012.Z |
—
|
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: 012.Z | Statement: [Drammenselva, watercourseId, 012.Z]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseId Context triple: [Drammenselva, watercourseId, 012.Z]
-
A.
watercourseName
Indicates the name assigned to a river, stream, or other flowing body of water in the relationship.
-
B.
sourceOfWatercourse
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
-
C.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
D.
inflowWatercourse
Indicates that one watercourse flows into or feeds another water body or watercourse.
-
E.
outflowWatercourse
Indicates the watercourse (such as a river, stream, or channel) into which a body of water flows out.
- F. None of above. chosen
Provenance (4 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35200263081909bb326a4d7a8db99 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:17 p.m.