Triple
T15825481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot Point, Alaska |
E383729
|
entity |
| Predicate | nearbyFishery |
P119787
|
FINISHED |
| Object | Bristol Bay 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: Bristol Bay salmon fishery | Statement: [Pilot Point, Alaska, nearbyFishery, Bristol Bay salmon fishery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyFishery Context triple: [Pilot Point, Alaska, nearbyFishery, Bristol Bay salmon fishery]
-
A.
fisheriesProduct
Indicates that something is a product derived from fishing activities or the harvesting of aquatic organisms.
-
B.
commercialFishingAllowed
Indicates that engaging in commercial fishing activities is permitted in the specified area or context.
-
C.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
D.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
E.
nearbyPortFacility
Indicates that one entity is located close to or in the immediate vicinity of a port facility.
- F. None of above. chosen
Provenance (4 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e602e5481908baa71c3d9b2008f |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007647f908190adb178c68c7bb7cf |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:49 a.m.