Triple
T26814769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dakota Access Pipeline |
E672094
|
entity |
| Predicate | nearWaterSource |
P49291
|
FINISHED |
| Object | Lake Oahe |
—
|
NE NERFINISHED |
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: Lake Oahe | Statement: [Dakota Access Pipeline, nearWaterSource, Lake Oahe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearWaterSource Context triple: [Dakota Access Pipeline, nearWaterSource, Lake Oahe]
-
A.
hasNearbyWater
chosen
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
B.
nearbyWatercourse
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
-
C.
hasNearbyWaterInfrastructure
Indicates that a location or entity is situated close to water-related infrastructure such as pipes, treatment facilities, or distribution systems.
-
D.
waterBodyCreatedNearby
Indicates that a water body has been formed or established in close spatial proximity to a specified reference location or entity.
-
E.
waterSource
Indicates that one entity serves as the source or provider of water for 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a849f4481908de0e3bc4f61da1c |
completed | May 2, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:31 a.m.