Triple
T6391486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upsala Glacier |
E143836
|
entity |
| Predicate | hasIceType |
P70342
|
FINISHED |
| Object | temperate ice |
—
|
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: temperate ice | Statement: [Upsala Glacier, hasIceType, temperate ice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIceType Context triple: [Upsala Glacier, hasIceType, temperate ice]
-
A.
hasIceClass
Indicates that an object (typically a vessel or structure) is assigned a specific ice classification denoting its capability to operate in icy or ice-infested waters.
-
B.
hasIceShelf
Indicates that a glacier, ice sheet, or coastline possesses an attached floating extension of ice known as an ice shelf.
-
C.
hasIceSheetType
Indicates that an entity is associated with or characterized by a specific type or classification of ice sheet.
-
D.
hasTypicalSeaIceType
Indicates the characteristic or commonly occurring type of sea ice associated with a given location or context.
-
E.
hasIceSource
Indicates that one entity serves as the origin or provider of ice for another entity.
- 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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0687db4b881909dd84d5a947cc3e3 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:34 p.m.