Triple
T30758422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pink salmon |
E783154
|
entity |
| Predicate | fisheryProduct |
P92956
|
FINISHED |
| Object | canned salmon |
—
|
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: canned salmon | Statement: [Pink salmon, fisheryProduct, canned salmon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fisheryProduct Context triple: [Pink salmon, fisheryProduct, canned salmon]
-
A.
fisheriesProduct
chosen
Indicates that something is a product derived from fishing activities or the harvesting of aquatic organisms.
-
B.
aquacultureProduct
Indicates that something is a product derived from aquaculture activities, such as the farming or cultivation of aquatic organisms.
-
C.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
D.
fishTypeProduced
Indicates that one entity produces, yields, or is the source of a particular type of fish as an output or product.
-
E.
seafoodSpecialty
Indicates that one entity specializes in preparing, serving, or producing seafood as a primary focus or notable expertise.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f994b5081908ec02116df654bde |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:39 p.m.