Triple
T29981270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunrise area of Mount Rainier National Park |
E761598
|
entity |
| Predicate | hasHighestElevationRoadAccess |
P57868
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sunrise area of Mount Rainier National Park, hasHighestElevationRoadAccess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestElevationRoadAccess Context triple: [Sunrise area of Mount Rainier National Park, hasHighestElevationRoadAccess, true]
-
A.
hasAccessRoadsTo
Indicates that there exist one or more roads providing direct vehicular access from one location or site to another.
-
B.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
C.
hasValleyAccessTo
Indicates that one location can be reached from another specifically by traveling through a valley or valley-based route.
-
D.
isMountainRoad
Indicates that a given road is classified as a mountain road, typically traversing or situated within mountainous terrain.
-
E.
highestRoadPassIn
chosen
Indicates that a location contains the highest-elevation road pass within a specified area or region.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 29, 2026, 6:35 p.m.