Triple
T17080086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Peak |
E414447
|
entity |
| Predicate | typicalStartingTrailhead |
P37604
|
FINISHED |
| Object | Castle Creek trailhead |
—
|
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: Castle Creek trailhead | Statement: [Castle Peak, typicalStartingTrailhead, Castle Creek trailhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStartingTrailhead Context triple: [Castle Peak, typicalStartingTrailhead, Castle Creek trailhead]
-
A.
typicalAscentStartPoint
chosen
Indicates the usual or most common location from which an ascent or climb is begun.
-
B.
typicalStartElevation
Indicates the usual or characteristic elevation at which something (such as a route, feature, or activity) typically begins.
-
C.
trailheadIn
Indicates that a trailhead is located within or at a specific place or area.
-
D.
tourStartingPoint
Indicates the location or point from which a tour begins.
-
E.
hasTrailheads
Indicates that one location or area contains or provides access points where trails begin.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe24a6481908b4596c95220df4a |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.