Triple
T16943936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalama River |
E411018
|
entity |
| Predicate | hasSalmonRuns |
P91615
|
FINISHED |
| Object | spring Chinook |
—
|
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: spring Chinook | Statement: [Kalama River, hasSalmonRuns, spring Chinook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSalmonRuns Context triple: [Kalama River, hasSalmonRuns, spring Chinook]
-
A.
hasSteelheadRun
Indicates that a location or waterway supports or experiences a migratory run of steelhead trout.
-
B.
salmonRun
chosen
Indicates a migratory movement in which salmon travel, typically upstream, to reach spawning or feeding areas.
-
C.
hasBlueRuns
Indicates that the subject possesses or is associated with runs (e.g., streaks, paths, or sequences) that are characterized by the color blue.
-
D.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
E.
hasFishingSeason
Indicates that there is a defined time period during which fishing for a particular resource or in a particular area is permitted or regulated.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb08da88190b07c32652bbc1534 |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.