Triple
T24152055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tummel hydroelectric scheme |
E598562
|
entity |
| Predicate | usesTributary |
P154796
|
FINISHED |
| Object | River Garry |
—
|
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: River Garry | Statement: [Tummel hydroelectric scheme, usesTributary, River Garry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTributary Context triple: [Tummel hydroelectric scheme, usesTributary, River Garry]
-
A.
hasTributaryRelationsWith
Indicates that one entity maintains a tributary relationship with another, typically involving regular payments or offerings in exchange for protection, favor, or acknowledgment of superiority.
-
B.
hasTributaryType
Indicates that one watercourse is classified as a specific type of tributary in relation to another water body.
-
C.
hasTributaryRelation
Indicates a relationship where one entity serves as a tributary, paying regular tribute or acknowledging subordination to another entity.
-
D.
containsTributariesOf
Indicates that one water body or drainage system includes within it the tributary streams or rivers of another.
-
E.
receivesTributariesFrom
Indicates that one entity serves as the main body that is fed or supplemented by incoming tributary entities.
- F. None of above. chosen
Provenance (4 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e1e5748190bcc6681d409dcc05 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 11:30 p.m.