Triple
T23158598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clyde Dam |
E578515
|
entity |
| Predicate | reservoirCreatedByInundationOf |
P25354
|
FINISHED |
| Object | parts of Cromwell Gorge |
—
|
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: parts of Cromwell Gorge | Statement: [Clyde Dam, reservoirCreatedByInundationOf, parts of Cromwell Gorge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservoirCreatedByInundationOf Context triple: [Clyde Dam, reservoirCreatedByInundationOf, parts of Cromwell Gorge]
-
A.
reservoirCreatedByDam
chosen
Indicates that a reservoir exists as a result of being formed or impounded by a specific dam.
-
B.
reservoirCreated
Indicates that a reservoir has been brought into existence, typically through construction or formation by some agent or process.
-
C.
reservoir
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
D.
riverImpounded
Indicates that a river’s natural flow is obstructed or controlled, typically by a dam or similar structure, creating an impoundment such as a reservoir.
-
E.
reservoirAlsoKnownAs
Indicates that a reservoir is referred to by an alternative name or alias.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efeddd48190b6d03d2146583dcc |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:02 p.m.