Triple
T27394577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erebus Glacier |
E691640
|
entity |
| Predicate | iceType |
P82510
|
FINISHED |
| Object | cold-based ice (predominantly) |
—
|
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: cold-based ice (predominantly) | Statement: [Erebus Glacier, iceType, cold-based ice (predominantly)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iceType Context triple: [Erebus Glacier, iceType, cold-based ice (predominantly)]
-
A.
iceClass
Indicates a classification relationship specifying the level or category of ice-strengthening or ice-navigation capability assigned to a vessel or structure.
-
B.
iceFeature
Indicates a relationship where a geographic or environmental feature is composed of, covered by, or characterized by ice.
-
C.
iceStrengthened
Indicates that an entity has been made stronger, reinforced, or enhanced through the application or influence of ice.
-
D.
SolidICEType
chosen
Indicates that something is classified as a type or category of solid ice.
-
E.
servedWithIceType
Indicates that a beverage or drink item is accompanied by and served with a specified type of 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62caf1be88190b61397557e09c0e9 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:27 p.m.