Triple
T22812321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Fork Big Creek Trail |
E564714
|
entity |
| Predicate | summitAreaAccess |
P27622
|
FINISHED |
| Object | Arc Dome summit area |
—
|
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: Arc Dome summit area | Statement: [North Fork Big Creek Trail, summitAreaAccess, Arc Dome summit area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitAreaAccess Context triple: [North Fork Big Creek Trail, summitAreaAccess, Arc Dome summit area]
-
A.
summitAccessibleFrom
chosen
Indicates that a summit can be reached or accessed starting from a specified location or route.
-
B.
hasSummitAccess
Indicates that an entity is permitted or able to reach or enter the summit or highest level of a specified place, system, or structure.
-
C.
summitAccessInfrastructure
Indicates the presence or provision of infrastructure that enables access to a summit, such as paths, roads, or transport facilities.
-
D.
hasSummitArea
Indicates that an entity has a specific area or surface extent associated with its summit or highest point.
-
E.
summitView
Indicates a vantage point or perspective that is obtained from the top or highest point of something, such as a mountain or structure.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d60f5948190b624b2dab04cbe63 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:32 p.m.