Triple
T16262823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svellnosbreen |
E394795
|
entity |
| Predicate | hasGlaciologicalStatus |
P41455
|
FINISHED |
| Object | retreating glacier |
—
|
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: retreating glacier | Statement: [Svellnosbreen, hasGlaciologicalStatus, retreating glacier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlaciologicalStatus Context triple: [Svellnosbreen, hasGlaciologicalStatus, retreating glacier]
-
A.
glaciersStatus
chosen
Indicates the current condition or state of glaciers, such as their size, stability, or rate of change.
-
B.
hasGlacier
Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
-
C.
isGlaciologicallyRelatedTo
Indicates a relationship where two entities are connected through glaciological processes, features, or phenomena (such as ice dynamics, glacial formation, movement, or melt).
-
D.
isGlacialLake
Indicates that a body of water is classified as a glacial lake, formed by the action or presence of glaciers.
-
E.
glaciologicalRole
Indicates the specific function, activity, or responsibility an entity has within the study or processes of glaciers and ice.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c5583c8190901e892238cf8dbd |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.