Triple
T34116617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebastes entomelas |
E874989
|
entity |
| Predicate | fisheriesUse |
P33588
|
FINISHED |
| Object | commercial fisheries |
—
|
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: commercial fisheries | Statement: [Sebastes entomelas, fisheriesUse, commercial fisheries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fisheriesUse Context triple: [Sebastes entomelas, fisheriesUse, commercial fisheries]
-
A.
fisheries
Indicates that an entity is engaged in, associated with, or responsible for the activity, management, or industry of catching, raising, or harvesting fish and other aquatic organisms.
-
B.
fisheryType
chosen
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.
fisheriesProduct
Indicates that something is a product derived from fishing activities or the harvesting of aquatic organisms.
-
E.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70cea91f481909e71cffce7ee6770 |
completed | May 3, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:53 a.m.