Triple
T20960103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merwin Dam |
E516215
|
entity |
| Predicate | fishPassageMitigation |
P130189
|
FINISHED |
| Object | Lewis River basin fish programs |
—
|
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: Lewis River basin fish programs | Statement: [Merwin Dam, fishPassageMitigation, Lewis River basin fish programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishPassageMitigation Context triple: [Merwin Dam, fishPassageMitigation, Lewis River basin fish programs]
-
A.
fishPassage
Indicates that a water structure or feature allows fish to move or migrate through or past it.
-
B.
blocksFishMigration
Indicates that one entity obstructs or prevents the movement or migratory passage of fish between habitats.
-
C.
hasFishPassage
Indicates that there exists a structure or feature that allows fish to move or migrate through, past, or around a barrier such as a dam or weir.
-
D.
hasFishPassageIssues
Indicates that there are problems or barriers affecting the ability of fish to move through a waterway or structure.
-
E.
hasFishProtectionMeasures
chosen
Indicates that there are specific measures or practices in place to protect fish populations or their habitats.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb6e50988190a564d2aaf1a9bc54 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1:30 p.m.