Triple
T28437962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fall River Entrance Station of Rocky Mountain National Park |
E715622
|
entity |
| Predicate | accessesRoad |
P137979
|
FINISHED |
| Object | Trail Ridge Road |
—
|
NE NERFINISHED |
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: Trail Ridge Road | Statement: [Fall River Entrance Station of Rocky Mountain National Park, accessesRoad, Trail Ridge Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesRoad Context triple: [Fall River Entrance Station of Rocky Mountain National Park, accessesRoad, Trail Ridge Road]
-
A.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
B.
roadAccessArea
chosen
Indicates that an area is designated for or provides access to a road, such as for entry, exit, or connection.
-
C.
roadAccessFrom
Indicates that one location can be reached from another via a usable road connection.
-
D.
hasSeparateAccessRoadFor
Indicates that one entity is served by its own distinct access road that is separate from the access road used by another entity.
-
E.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 1:44 a.m.