Triple
T26814752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dakota Access Pipeline |
E672094
|
entity |
| Predicate | originBasin |
P108767
|
FINISHED |
| Object | Bakken formation |
—
|
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: Bakken formation | Statement: [Dakota Access Pipeline, originBasin, Bakken formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originBasin Context triple: [Dakota Access Pipeline, originBasin, Bakken formation]
-
A.
sourceBasin
Indicates that one entity is the drainage basin or watershed from which another entity (such as a river segment or water body) originates or receives its source waters.
-
B.
basinOfFormation
chosen
Indicates that one entity is the geological basin in which another entity was formed or originated.
-
C.
basinFor
Indicates that something serves as a basin or receptacle specifically intended for collecting, holding, or draining another entity.
-
D.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
-
E.
basinPartOf
Indicates that one basin is a component or subdivision of a larger basin or basin system.
- 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_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 27, 2026, 4:31 a.m.