Triple
T3990366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Stewardship Council |
E86973
|
entity |
| Predicate | regulatoryPowerOver |
P31477
|
FINISHED |
| Object | covered actions in the Delta |
—
|
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: covered actions in the Delta | Statement: [Delta Stewardship Council, regulatoryPowerOver, covered actions in the Delta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryPowerOver Context triple: [Delta Stewardship Council, regulatoryPowerOver, covered actions in the Delta]
-
A.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
-
B.
typeOfPowerGranted
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
-
C.
hasLegislativePower
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
-
D.
scopeOfPower
chosen
Indicates the range or extent of authority, control, or decision-making power that an entity is permitted to exercise.
-
E.
regulatesIn
Indicates that one entity controls, modulates, or influences the activity, expression, or behavior of another entity within a system or process.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.