Triple
T33765807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochsa River |
E865225
|
entity |
| Predicate | typicalWhitewaterDifficulty |
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: [Lochsa River, typicalWhitewaterDifficulty, Class III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWhitewaterDifficulty Context triple: [Lochsa River, typicalWhitewaterDifficulty, Class III]
-
A.
hasRaftingDifficulty
Indicates that an entity is associated with a specific level of rafting difficulty.
-
B.
typicalDifficulty
Indicates the usual or characteristic level of difficulty associated with performing an action or achieving a particular outcome.
-
C.
typicalSnowDifficulty
Indicates the usual or characteristic level of difficulty associated with snow conditions for an activity, route, or location.
-
D.
hasWhitewaterClassification
chosen
Indicates that a river or waterway segment is assigned a specific whitewater difficulty class according to a recognized classification system.
-
E.
typeOfWaterfall
Indicates that one entity is a specific kind or category of waterfall in relation to another 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:45 a.m.