Triple
T35380721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wright Trail |
E1022636
|
entity |
| Predicate | primaryAscentTo |
P190430
|
FINISHED |
| Object | Goose Eye Mountain |
E308834
|
NE 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: Goose Eye Mountain | Statement: [Wright Trail, primaryAscentTo, Goose Eye Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAscentTo Context triple: [Wright Trail, primaryAscentTo, Goose Eye Mountain]
-
A.
notableAscent
Indicates that an entity is recognized for a significant rise, climb, or upward journey, such as an important ascent of a mountain or similar elevation.
-
B.
typeOfAscent
Indicates the specific manner or style in which an ascent (such as a climb or upward movement) is performed or categorized.
-
C.
onTypicalAscentRouteTo
chosen
Indicates that one entity lies along the standard or commonly used ascent route leading to another entity, typically in a climbing or mountaineering context.
-
D.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
-
E.
climbsTo
Indicates that one entity moves upward, typically with effort or by climbing, until it reaches another entity or a higher position.
- F. None of above.
Provenance (4 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3836a92de8819093bba73be2feefce |
completed | June 21, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.