Triple
T26814721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dakota Access Pipeline protests |
E672093
|
entity |
| Predicate | formOfAction |
P161497
|
FINISHED |
| Object | legal challenges |
—
|
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: legal challenges | Statement: [Dakota Access Pipeline protests, formOfAction, legal challenges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formOfAction Context triple: [Dakota Access Pipeline protests, formOfAction, legal challenges]
-
A.
formOfAction
chosen
Indicates that one action is a specific manner, variant, or implementation of another more general action.
-
B.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against another entity.
-
C.
actionBy
Indicates that a particular action is performed or carried out by a specified agent or entity.
-
D.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
E.
fromAct
Indicates that an entity originates from, is produced by, or results from a specified action or event.
- 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_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 4:31 a.m.