Triple
T12374551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwards Dam |
E295087
|
entity |
| Predicate | FERCDecision |
P91324
|
FINISHED |
| Object | ordered removal after license denial |
—
|
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: ordered removal after license denial | Statement: [Edwards Dam, FERCDecision, ordered removal after license denial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FERCDecision Context triple: [Edwards Dam, FERCDecision, ordered removal after license denial]
-
A.
decisionHolding
chosen
Indicates that an entity has made, issued, or is responsible for a particular formal decision or ruling.
-
B.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
C.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
D.
decisionImplementedBy
Indicates that a particular decision is carried out, executed, or put into effect by a specified agent or entity.
-
E.
decider
Indicates that an entity is the one who makes a choice or decision in a given situation 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93fa8ca7c8190b3f8e9c2ec23e837 |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.