Triple
T1403937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mist Trail and John Muir Trail to Sub Dome |
E31646
|
entity |
| Predicate | approachRouteFor |
P6174
|
FINISHED |
| Object | Half Dome summit via cables |
—
|
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: Half Dome summit via cables | Statement: [Mist Trail and John Muir Trail to Sub Dome, approachRouteFor, Half Dome summit via cables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachRouteFor Context triple: [Mist Trail and John Muir Trail to Sub Dome, approachRouteFor, Half Dome summit via cables]
-
A.
approachRoute
chosen
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
B.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
C.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
D.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
E.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3a0330c8190b22452d29c79fcf4 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.