Triple
T17265794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Moran |
E419122
|
entity |
| Predicate | standardRouteApproach |
P6174
|
FINISHED |
| Object | canoe or boat across Jackson Lake |
—
|
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: canoe or boat across Jackson Lake | Statement: [Mount Moran, standardRouteApproach, canoe or boat across Jackson Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardRouteApproach Context triple: [Mount Moran, standardRouteApproach, canoe or boat across Jackson Lake]
-
A.
standardRouteStartsFrom
Indicates that a standard or predefined route has its starting point at a specified location or entity.
-
B.
standardApproach
Indicates that an entity uses or follows a commonly accepted, conventional, or typical method for addressing a task or problem.
-
C.
approachRoute
chosen
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
D.
standardRouteGain
Indicates the amount of benefit, profit, or advantage obtained through following a normal or predefined route or process.
-
E.
standardRouteClass
Indicates that a route is classified according to a predefined standard category or class used for routing or transportation.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f44ec7c81909a925fc8692b0a6c |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.