Triple
T8846692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chum salmon |
E210522
|
entity |
| Predicate | dietAtSea |
P20746
|
FINISHED |
| Object | zooplankton |
—
|
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: zooplankton | Statement: [Chum salmon, dietAtSea, zooplankton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dietAtSea Context triple: [Chum salmon, dietAtSea, zooplankton]
-
A.
seafoodSpecialty
Indicates that one entity specializes in preparing, serving, or producing seafood as a primary focus or notable expertise.
-
B.
Seafood Watch
Indicates a relationship in which an entity evaluates and advises on the environmental sustainability of seafood choices or fisheries.
-
C.
foodSources
chosen
Indicates a relationship where one entity serves as a source of food or nourishment for another entity.
-
D.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
E.
fishPassage
Indicates that a water structure or feature allows fish to move or migrate through or past it.
- 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60a7c518819095399976148e1b9a |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:48 p.m.