Triple
T7615308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braeriach |
E172346
|
entity |
| Predicate | usualAscentFrom |
P37604
|
FINISHED |
| Object | Sugar Bowl car park |
—
|
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: Sugar Bowl car park | Statement: [Braeriach, usualAscentFrom, Sugar Bowl car park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usualAscentFrom Context triple: [Braeriach, usualAscentFrom, Sugar Bowl car park]
-
A.
usualFirstAscentBy
Indicates that the referenced entity is the person or party who is typically credited with making the first ascent of a particular route, peak, or climbing objective.
-
B.
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.
-
C.
usuallyClimbedAs
Indicates that an object, route, or feature is most commonly or traditionally ascended in a particular style, manner, or configuration.
-
D.
typicalAscentStartPoint
chosen
Indicates the usual or most common location from which an ascent or climb is begun.
-
E.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
- 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa4392e881908ed1ab3f64b41600 |
completed | March 27, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:55 p.m.