Triple
T18696642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rifugio Federico Chabod |
E457131
|
entity |
| Predicate | typicalStartingPointFor |
P37604
|
FINISHED |
| Object | normal route to Gran Paradiso north 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 to Gran Paradiso north side | Statement: [Rifugio Federico Chabod, typicalStartingPointFor, normal route to Gran Paradiso north side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStartingPointFor Context triple: [Rifugio Federico Chabod, typicalStartingPointFor, normal route to Gran Paradiso north side]
-
A.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
B.
isStartingPointOf
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
-
C.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
D.
typicalAscentStartPoint
chosen
Indicates the usual or most common location from which an ascent or climb is begun.
-
E.
tourStartingPoint
Indicates the location or point from which a tour begins.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e8bc408190ab41b3c21003c249 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.