Triple
T16333440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Salmon River |
E396612
|
entity |
| Predicate | whitewaterClassRange |
P99934
|
FINISHED |
| Object | Class III |
—
|
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: Class III | Statement: [White Salmon River, whitewaterClassRange, Class III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: whitewaterClassRange Context triple: [White Salmon River, whitewaterClassRange, Class III]
-
A.
hasWhitewaterClassification
chosen
Indicates that a river or waterway segment is assigned a specific whitewater difficulty class according to a recognized classification system.
-
B.
hasRaftingDifficulty
Indicates that an entity is associated with a specific level of rafting difficulty.
-
C.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
D.
typeOfWaterfall
Indicates that one entity is a specific kind or category of waterfall in relation to another entity.
-
E.
waterwayWidth
Indicates the measured width of a waterway, typically the distance across it from one bank or edge to the opposite.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e1da1081909bec6e77e6109dce |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.