Triple
T27255045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denison Dam Power Plant |
E687588
|
entity |
| Predicate | regulatesOutflowFrom |
P20749
|
FINISHED |
| Object | Lake Texoma |
—
|
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: Lake Texoma | Statement: [Denison Dam Power Plant, regulatesOutflowFrom, Lake Texoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesOutflowFrom Context triple: [Denison Dam Power Plant, regulatesOutflowFrom, Lake Texoma]
-
A.
regulatesOutflowOf
chosen
Indicates that one entity controls, modulates, or governs the rate or amount of outflow from another entity.
-
B.
regulatesFlowBetween
Indicates a relationship where one entity controls, directs, or modulates the movement or transfer of something (such as material, energy, or information) between two other entities.
-
C.
regulatesFlowFor
Indicates that one entity controls, directs, or manages the rate or movement of another entity’s flow.
-
D.
regulatesFlowNear
Indicates that one entity controls, influences, or manages the movement or rate of flow of another entity in its nearby vicinity.
-
E.
outflow
Indicates the movement or discharge of something from an origin or source to the outside or to another location.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 10:48 a.m.