Triple
T31046115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glines Canyon Dam |
E791129
|
entity |
| Predicate | riverRestored |
P43697
|
FINISHED |
| Object | Elwha River free-flowing condition |
—
|
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: Elwha River free-flowing condition | Statement: [Glines Canyon Dam, riverRestored, Elwha River free-flowing condition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverRestored Context triple: [Glines Canyon Dam, riverRestored, Elwha River free-flowing condition]
-
A.
waterSourceRestored
chosen
Indicates that a previously unavailable or degraded water source has been returned to a functional and usable condition.
-
B.
reachedRiver
Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
-
C.
riverFormed
Indicates that a river came into existence or was created, typically as a result of natural geological or hydrological processes.
-
D.
riverbedDivertedTo
Indicates that the natural course of a riverbed has been redirected or channeled toward another location or pathway.
-
E.
impactedRiver
Indicates that one entity has caused a significant effect, alteration, or disturbance to a river or its conditions.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 29, 2026, 8:59 p.m.