Triple
T11733879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antisana Volcano |
E278974
|
entity |
| Predicate | glacierRetreatCause |
P101057
|
FINISHED |
| Object | climate change |
—
|
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: climate change | Statement: [Antisana Volcano, glacierRetreatCause, climate change]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glacierRetreatCause Context triple: [Antisana Volcano, glacierRetreatCause, climate change]
-
A.
hasGlacialRetreat
Indicates that a glacier has decreased in size or extent over time, showing a retreat of its ice front or overall mass.
-
B.
glaciologySignificance
Indicates the degree to which something is important or relevant within the study of glaciers and related glacial processes.
-
C.
glaciologicalRole
Indicates the specific function, activity, or responsibility an entity has within the study or processes of glaciers and ice.
-
D.
iceMassLossContributesTo
Indicates that the loss of ice mass plays a causal role in producing or increasing another effect, condition, or process.
-
E.
glacierType
Indicates the specific classification or category of a glacier based on its form, dynamics, or setting.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4daa7f48190896fc7653e9dd70b |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.