Triple
T22311298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roaring Fork River |
E551518
|
entity |
| Predicate | recreationClassification |
P44008
|
FINISHED |
| Object | whitewater river |
—
|
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: whitewater river | Statement: [Roaring Fork River, recreationClassification, whitewater river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationClassification Context triple: [Roaring Fork River, recreationClassification, whitewater river]
-
A.
hasRecreationClassification
chosen
Indicates that an entity is assigned a specific type or category of recreational use or activity.
-
B.
recreationUseLevel
Indicates the intensity or degree to which an entity is used for recreational activities.
-
C.
recreationRegion
Indicates that a location or area is designated or used as a region for recreational activities.
-
D.
hasRecreationalAspect
Indicates that something includes, involves, or is characterized by a recreational or leisure-related component or purpose.
-
E.
recreationRegulation
Indicates rules, restrictions, or guidelines governing recreational activities or leisure use of a place or resource.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1574e7fc0819080e3e85001ab2c90 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.