Triple
T6522765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beinn an Òir |
E151224
|
entity |
| Predicate | hasTypicalAscentRoute |
P65032
|
FINISHED |
| Object | from Three Arch Bridge |
—
|
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: from Three Arch Bridge | Statement: [Beinn an Òir, hasTypicalAscentRoute, from Three Arch Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalAscentRoute Context triple: [Beinn an Òir, hasTypicalAscentRoute, from Three Arch Bridge]
-
A.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
-
B.
typicalAscentRouteVia
chosen
Indicates the usual or most commonly used route taken to ascend or reach a particular destination, such as a summit or high point.
-
C.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
-
D.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
E.
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.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad95c2c88190b800aaaa73f99210 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.