Triple
T32679665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warm Springs Dam |
E835536
|
entity |
| Predicate | fishSpeciesAffected |
P45992
|
FINISHED |
| Object | steelhead trout |
—
|
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: steelhead trout | Statement: [Warm Springs Dam, fishSpeciesAffected, steelhead trout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishSpeciesAffected Context triple: [Warm Springs Dam, fishSpeciesAffected, steelhead trout]
-
A.
fishFamily
Indicates that one entity is a member of the same biological family (taxonomic family) of fishes as the other entity.
-
B.
gameFish
Indicates a relationship where an animal is considered a fish that is commonly pursued or valued in recreational or sport fishing.
-
C.
fishPassage
Indicates that a water structure or feature allows fish to move or migrate through or past it.
-
D.
hasFishingSpecies
chosen
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
E.
fishTypeProduced
Indicates that one entity produces, yields, or is the source of a particular type of fish as an output or product.
- 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_69f3493134b48190aa3c8cb523bd3800 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7e7956c8190a3f54d6d6ff803f1 |
completed | May 3, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:09 a.m.