Triple
T30974739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon and Idaho |
E789199
|
entity |
| Predicate | shareOutdoorActivities |
P182069
|
FINISHED |
| Object | hiking in 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: hiking in Hells Canyon | Statement: [Oregon and Idaho, shareOutdoorActivities, hiking in Hells Canyon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareOutdoorActivities Context triple: [Oregon and Idaho, shareOutdoorActivities, hiking in Hells Canyon]
-
A.
outdoorDestinationFor
Indicates a relationship where one entity serves as an outdoor place or venue that another entity is intended to visit, use, or travel to.
-
B.
outdoorActivityType
Indicates the specific kind of outdoor activity associated with an entity or event.
-
C.
campCategory
Indicates the classification or type of camp to which an entity belongs (e.g., by purpose, style, or characteristics).
-
D.
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.
-
E.
recreationOpportunity
chosen
Indicates that one entity provides, enables, or is associated with a chance for recreational activities for 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
Created at: April 29, 2026, 8:55 p.m.