Triple
T34605326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aguilera volcano |
E888581
|
entity |
| Predicate | glacierInteraction |
P179688
|
FINISHED |
| Object | eruption–ice interaction potential |
—
|
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: eruption–ice interaction potential | Statement: [Aguilera volcano, glacierInteraction, eruption–ice interaction potential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glacierInteraction Context triple: [Aguilera volcano, glacierInteraction, eruption–ice interaction potential]
-
A.
glacierSystem
Indicates a relationship where entities participate in or belong to the same interconnected system of glaciers and related glacial components.
-
B.
hasGlacier
Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
-
C.
liesNearGlacier
Indicates that one entity is located in close physical proximity to a glacier.
-
D.
glacierType
Indicates the specific classification or category of a glacier based on its form, dynamics, or setting.
-
E.
glacierContext
Indicates that something occurs within, is associated with, or is defined by the environmental, geological, or situational context of a glacier.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2:03 a.m.