Triple
T3035198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goûter Hut |
E82991
|
entity |
| Predicate | typicalAscentRoute |
P2405
|
FINISHED |
| Object | normal route on Mont Blanc from the French side |
—
|
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: normal route on Mont Blanc from the French side | Statement: [Goûter Hut, typicalAscentRoute, normal route on Mont Blanc from the French side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAscentRoute Context triple: [Goûter Hut, typicalAscentRoute, normal route on Mont Blanc from the French side]
-
A.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
-
B.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
-
C.
climbingDifficultyStandardRoute
Indicates the level of difficulty associated with ascending via the standard or most commonly used route.
-
D.
secondAscentRoute
Indicates that the related route was used for the second recorded ascent of a particular peak or climbing objective.
-
E.
climbingRoute
chosen
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b2a40b48190bfa7cdbb0fbd87f8 |
completed | March 8, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.