Triple
T8846718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chum salmon |
E210522
|
entity |
| Predicate | habitatAtSea |
P2975
|
FINISHED |
| Object | coastal waters |
—
|
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: coastal waters | Statement: [Chum salmon, habitatAtSea, coastal waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: habitatAtSea Context triple: [Chum salmon, habitatAtSea, coastal waters]
-
A.
hasMarineEcoregion
Indicates that an entity is associated with, or located within, a specific marine ecoregion.
-
B.
hasMarineSpecies
Indicates that an entity contains, supports, or is associated with one or more marine species.
-
C.
isShallowSea
Indicates that a body of water is a shallow marine area, typically near coasts or continental shelves, rather than deep ocean.
-
D.
marineArea
chosen
Indicates a relationship where an entity is located in, associated with, or relevant to a specific marine or oceanic area.
-
E.
seaType
Indicates the specific classification or category of a sea associated with an entity.
- 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.