Triple
T8846720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chum salmon |
E210522
|
entity |
| Predicate | habitatInFreshwater |
P75237
|
FINISHED |
| Object | gravel-bottom streams |
—
|
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: gravel-bottom streams | Statement: [Chum salmon, habitatInFreshwater, gravel-bottom streams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: habitatInFreshwater Context triple: [Chum salmon, habitatInFreshwater, gravel-bottom streams]
-
A.
receivesFreshwaterFrom
Indicates that one entity is supplied with or obtains freshwater from another entity as its source.
-
B.
hasAquaticEcosystem
Indicates that an entity possesses, contains, or is associated with an ecosystem primarily based in water (such as rivers, lakes, wetlands, or oceans).
-
C.
locatedInWaterBodyType
chosen
Indicates that an entity is situated within or on a body of water of a specified type (e.g., lake, river, ocean).
-
D.
isFreshwaterBody
Indicates that the referenced body of water consists primarily of non-saline (fresh) water rather than saltwater.
-
E.
containsAquaticMembers
Indicates that a group or collection includes one or more members that live in or are adapted to aquatic environments.
- 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.