Triple
T18627650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rifugio Vittorio Emanuele II |
E455324
|
entity |
| Predicate | typicalAscentTimeFromValley |
P40570
|
FINISHED |
| Object | about 2–3 hours |
—
|
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 2–3 hours | Statement: [Rifugio Vittorio Emanuele II, typicalAscentTimeFromValley, about 2–3 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAscentTimeFromValley Context triple: [Rifugio Vittorio Emanuele II, typicalAscentTimeFromValley, about 2–3 hours]
-
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.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
-
D.
approximateAscentTimeFromRefuge
Indicates the estimated amount of time required to ascend from a specified refuge to a target point or destination.
-
E.
typicalAscentCombinedWith
Indicates that one ascent or climbing route is normally undertaken together with another as part of a standard or customary combined itinerary.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f0581f0819083c1aba9fb85f6a7 |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.