Triple
T2791576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mont Gerbier de Jonc |
E61939
|
entity |
| Predicate | averageAscentTime |
P40570
|
FINISHED |
| Object | about 30–45 minutes from parking |
—
|
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 30–45 minutes from parking | Statement: [Mont Gerbier de Jonc, averageAscentTime, about 30–45 minutes from parking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averageAscentTime Context triple: [Mont Gerbier de Jonc, averageAscentTime, about 30–45 minutes from parking]
-
A.
durationTypicalAscent
chosen
Indicates the typical amount of time required to complete an ascent.
-
B.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
C.
firstFreeAscentDuration
Indicates the length of time taken to complete the first free ascent of a route or climb.
-
D.
approximateAscentTimeFromRefuge
Indicates the estimated amount of time required to ascend from a specified refuge to a target point or destination.
-
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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdeea881481908d759c72798a50fb |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd025c948190a97dd961a9592bac |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.