Triple
T6761357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral Peak |
E154600
|
entity |
| Predicate | Southeast Buttress_rating |
P73334
|
FINISHED |
| Object | about 5.6 YDS |
—
|
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: about 5.6 YDS | Statement: [Cathedral Peak, Southeast Buttress_rating, about 5.6 YDS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Southeast Buttress_rating Context triple: [Cathedral Peak, Southeast Buttress_rating, about 5.6 YDS]
-
A.
secondAscentBy
Indicates that the related entity is the person, group, or expedition that made the second successful ascent of a particular route, peak, or climbing objective.
-
B.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
C.
isSecondarySummitOf
Indicates that one summit is a subsidiary or lesser peak that is topographically or hierarchically associated with a primary, higher summit.
-
D.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
-
E.
secondAscentRoute
Indicates that the related route was used for the second recorded ascent of a particular peak or climbing objective.
- F. None of above. chosen
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_69c688109c1c8190added9a221292af0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d3264b7481908816a4d19543fb7b |
completed | March 27, 2026, 6:57 p.m. |
Created at: March 27, 2026, 2:12 p.m.