Triple
T10796152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dungeness River |
E254711
|
entity |
| Predicate | isSalmonBearing |
P45992
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dungeness River, isSalmonBearing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSalmonBearing Context triple: [Dungeness River, isSalmonBearing, true]
-
A.
salmonType
Indicates that one entity is classified as a specific type or variety of salmon in relation to another entity.
-
B.
hasFishingSpecies
chosen
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
C.
hasPrimaryFishSpecies
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
D.
hasSteelheadRun
Indicates that a location or waterway supports or experiences a migratory run of steelhead trout.
-
E.
recognizedAsStateFishSince
Indicates that an entity has been officially designated as the state fish of a particular jurisdiction starting from a specified date.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d73332dbfc8190904434846957b618 |
completed | April 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.