Triple
T34708468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lummi Island Wild reefnet salmon fishery |
E1000570
|
entity |
| Predicate | fishingGearType |
P81811
|
FINISHED |
| Object | reefnet |
—
|
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: reefnet | Statement: [Lummi Island Wild reefnet salmon fishery, fishingGearType, reefnet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishingGearType Context triple: [Lummi Island Wild reefnet salmon fishery, fishingGearType, reefnet]
-
A.
fishingType
chosen
Indicates the specific method or style of fishing associated with an activity, event, or location.
-
B.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
C.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
-
D.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
E.
fisheriesProduct
Indicates that something is a product derived from fishing activities or the harvesting of aquatic organisms.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.