Triple
T13075014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glacier du Tour |
E329549
|
entity |
| Predicate | hasCrevasseRisk |
P51695
|
FINISHED |
| Object | seasonal |
—
|
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: seasonal | Statement: [Glacier du Tour, hasCrevasseRisk, seasonal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrevasseRisk Context triple: [Glacier du Tour, hasCrevasseRisk, seasonal]
-
A.
hasCrevasses
chosen
Indicates that the subject contains or is characterized by deep open cracks or fissures, typically in a surface such as ice or rock.
-
B.
hasClimbingHazard
Indicates that something presents a risk or danger specifically associated with climbing activities.
-
C.
liesNearGlacier
Indicates that one entity is located in close physical proximity to a glacier.
-
D.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
E.
hasGlacierAccess
Indicates that an entity has direct access to, or is reachable from, a glacier (e.g., via paths, routes, or physical adjacency).
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98117209081908272021013df2222 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9 p.m.