Triple
T9942506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristol Bay Borough |
E194116
|
entity |
| Predicate | primaryFishery |
P38078
|
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: [Bristol Bay Borough, primaryFishery, sockeye salmon fishery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFishery Context triple: [Bristol Bay Borough, primaryFishery, sockeye salmon fishery]
-
A.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
B.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
C.
majorFisheryRegion
Indicates that a location is recognized as a primary or significant region for fishing activities or fishery production.
-
D.
hasPrimaryFishSpecies
chosen
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
E.
commercialFishingAllowed
Indicates that engaging in commercial fishing activities is permitted in the specified area or context.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6124a188190b41feadb7b2f8922 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.