Triple
T8871150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malaspina Glacier (portion) |
E211157
|
entity |
| Predicate | hasParentGlacierType |
P16701
|
FINISHED |
| Object | piedmont 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: piedmont glacier | Statement: [Malaspina Glacier (portion), hasParentGlacierType, piedmont glacier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentGlacierType Context triple: [Malaspina Glacier (portion), hasParentGlacierType, piedmont glacier]
-
A.
hasGlacier
Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
-
B.
hasIceSheetType
Indicates that an entity is associated with or characterized by a specific type or classification of ice sheet.
-
C.
glacierType
chosen
Indicates the specific classification or category of a glacier based on its form, dynamics, or setting.
-
D.
hasGlaciatedPeak
Indicates that the subject has a peak that is covered or shaped by glacial ice.
-
E.
isGlaciologicallyRelatedTo
Indicates a relationship where two entities are connected through glaciological processes, features, or phenomena (such as ice dynamics, glacial formation, movement, or melt).
- 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_69ca838d3c7c8190a849566d5afd2b11 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6126d2f88190979ab25772ee657c |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:51 p.m.