Triple
T11624025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telescope Peak |
E276213
|
entity |
| Predicate | standardRouteType |
P75679
|
FINISHED |
| Object | hiking trail |
—
|
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: hiking trail | Statement: [Telescope Peak, standardRouteType, hiking trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardRouteType Context triple: [Telescope Peak, standardRouteType, hiking trail]
-
A.
primaryRouteType
chosen
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
-
B.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
C.
isStandardRouteOn
Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
-
D.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
E.
standardApproach
Indicates that an entity uses or follows a commonly accepted, conventional, or typical method for addressing a task or problem.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a122a3708190ab6513dad4c4fde7 |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:39 p.m.