Triple
T23947149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corin Dam |
E602943
|
entity |
| Predicate | regulatesFlowsIn |
P20749
|
FINISHED |
| Object | Cotter River system |
—
|
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: Cotter River system | Statement: [Corin Dam, regulatesFlowsIn, Cotter River system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesFlowsIn Context triple: [Corin Dam, regulatesFlowsIn, Cotter River system]
-
A.
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.
-
B.
regulatesFlowFor
Indicates that one entity controls, directs, or manages the rate or movement of another entity’s flow.
-
C.
regulatesOutflowOf
chosen
Indicates that one entity controls, modulates, or governs the rate or amount of outflow from another entity.
-
D.
managesFlowsFor
Indicates that one entity is responsible for overseeing, controlling, or coordinating the flows or flow-related processes of another entity.
-
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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02ee0288190b58fd71b9cc65964 |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:17 p.m.