Triple
T6745062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarkston, Washington |
E154187
|
entity |
| Predicate | primaryOutdoorAttraction |
P47568
|
FINISHED |
| Object | access to Hells Canyon |
—
|
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: access to Hells Canyon | Statement: [Clarkston, Washington, primaryOutdoorAttraction, access to Hells Canyon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOutdoorAttraction Context triple: [Clarkston, Washington, primaryOutdoorAttraction, access to Hells Canyon]
-
A.
outdoorVenue
Indicates that an event, activity, or gathering takes place at a location situated outdoors rather than inside a building or enclosed structure.
-
B.
outdoorSection
Indicates that one entity is a section, area, or portion that is located outdoors or in an open-air environment relative to another entity.
-
C.
localNatureSite
chosen
Indicates that a location is designated as a natural site of local significance or interest.
-
D.
outdoorActivityType
Indicates the specific kind of outdoor activity associated with an entity or event.
-
E.
containsNaturalPark
Indicates that one entity geographically includes or encompasses a natural park within its boundaries.
- 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_69c6880ef37881909268a5a7299b9293 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1b74ae081908575c4e47c0ef297 |
completed | March 27, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:10 p.m.