Triple
T26814772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dakota Access Pipeline |
E672094
|
entity |
| Predicate | constructionAdvancedBy |
P167107
|
FINISHED |
| Object | Donald Trump administration |
—
|
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: Donald Trump administration | Statement: [Dakota Access Pipeline, constructionAdvancedBy, Donald Trump administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionAdvancedBy Context triple: [Dakota Access Pipeline, constructionAdvancedBy, Donald Trump administration]
-
A.
constructionBase
Indicates that one entity serves as the foundational structure or base upon which another entity is constructed or built.
-
B.
constructionExpanded
Indicates that a construction project or structure has been enlarged or extended beyond its original size or scope.
-
C.
constructionDirection
Indicates the orientation or path along which a structure is built or assembled.
-
D.
constructionType
Indicates the specific method or style by which something is built or constructed.
-
E.
constructionAdaptation
Indicates a modification or adjustment made to a construction or built structure to meet new requirements, conditions, or functions.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 27, 2026, 4:31 a.m.