Triple
T1951480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opalescent River |
E42166
|
entity |
| Predicate | recreationZone |
P5383
|
FINISHED |
| Object | High Peaks Wilderness backcountry |
—
|
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: High Peaks Wilderness backcountry | Statement: [Opalescent River, recreationZone, High Peaks Wilderness backcountry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationZone Context triple: [Opalescent River, recreationZone, High Peaks Wilderness backcountry]
-
A.
hasRecreationalArea
chosen
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
B.
recreationRegulation
Indicates rules, restrictions, or guidelines governing recreational activities or leisure use of a place or resource.
-
C.
hasRecreationFacility
Indicates that one entity provides, contains, or is equipped with a recreational facility for use by another entity or by the public.
-
D.
typicalGameLocation
Indicates the usual or characteristic place where a game is played or takes place.
-
E.
arenaType
Indicates the specific kind or category of arena associated with an entity or event.
- 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb34eb5748190a3ac395252951eba |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff3eda88190b643994cb4dfb8df |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.