Triple
T26480616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windjoch |
E664671
|
entity |
| Predicate | glacierContext |
P160788
|
FINISHED |
| Object | surrounded by glaciated terrain |
—
|
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: surrounded by glaciated terrain | Statement: [Windjoch, glacierContext, surrounded by glaciated terrain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glacierContext Context triple: [Windjoch, glacierContext, surrounded by glaciated terrain]
-
A.
glacierSystem
Indicates a relationship where entities participate in or belong to the same interconnected system of glaciers and related glacial components.
-
B.
glacierCode
Indicates a classification or identifier assigned to a glacier, linking it to a specific code used for cataloging or reference.
-
C.
standardApproachGlacier
Indicates a glacier that is typically used as the main or customary route of approach to a mountain or climbing objective.
-
D.
hasGlacier
Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
-
E.
glaciationCenter
Indicates the location that serves as the primary source or focal point from which glaciation originates or is organized.
- F. None of above. chosen
Provenance (4 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612fa3f4481908d1db59213f734d2 |
completed | May 2, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f604120e848190b516c29b781d19cc |
completed | May 2, 2026, 2:02 p.m. |
Created at: April 27, 2026, 12:26 a.m.