Triple
T17819451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naknek River |
E444936
|
entity |
| Predicate | hasPrimaryFishery |
P56070
|
FINISHED |
| Object | sockeye salmon fishery |
—
|
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: sockeye salmon fishery | Statement: [Naknek River, hasPrimaryFishery, sockeye salmon fishery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryFishery Context triple: [Naknek River, hasPrimaryFishery, sockeye salmon fishery]
-
A.
hasPrimaryFishSpecies
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
B.
containsFishery
chosen
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
C.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
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.
hasFishingCommunities
Indicates that there exist communities in a given area or entity whose livelihoods or primary activities are based on fishing.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e489101aa48190a1439d8cb683bba9 |
completed | April 19, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:15 a.m.