Triple
T23276894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pukaki Dam |
E588745
|
entity |
| Predicate | managesOutflowTo |
P90533
|
FINISHED |
| Object | Waitaki River |
—
|
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: Waitaki River | Statement: [Pukaki Dam, managesOutflowTo, Waitaki River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesOutflowTo Context triple: [Pukaki Dam, managesOutflowTo, Waitaki River]
-
A.
managesFlowTo
chosen
Indicates that one entity controls, regulates, or directs the movement or distribution of something (such as data, resources, or materials) to another entity.
-
B.
regulatesOutflowOf
Indicates that one entity controls, modulates, or governs the rate or amount of outflow from another entity.
-
C.
finalOutflowTo
Indicates the ultimate destination or receiving point to which something (such as resources, funds, or outputs) is finally transferred or discharged.
-
D.
managesFlowsFor
Indicates that one entity is responsible for overseeing, controlling, or coordinating the flows or flow-related processes of another entity.
-
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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19578adf48190bdb129a55f86172c |
completed | April 29, 2026, 5:22 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:48 p.m.