Triple
T8556817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coos River |
E202589
|
entity |
| Predicate | hasRecreationalFishSpecies |
P45992
|
FINISHED |
| Object | Chinook salmon |
—
|
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: Chinook salmon | Statement: [Coos River, hasRecreationalFishSpecies, Chinook salmon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalFishSpecies Context triple: [Coos River, hasRecreationalFishSpecies, Chinook salmon]
-
A.
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.
-
B.
hasPrimaryFishSpecies
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
C.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
D.
recognizedAsStateFishSince
Indicates that an entity has been officially designated as the state fish of a particular jurisdiction starting from a specified date.
-
E.
hasFishCountingFacility
Indicates that a location or structure is equipped with a facility specifically designed for counting fish.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe946d1408190adc7dfb7b2173f9d |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.