Triple
T34687385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lautaro volcano |
E890788
|
entity |
| Predicate | glacialFeature |
P8808
|
FINISHED |
| Object | heavily crevassed ice cover |
—
|
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: heavily crevassed ice cover | Statement: [Lautaro volcano, glacialFeature, heavily crevassed ice cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glacialFeature Context triple: [Lautaro volcano, glacialFeature, heavily crevassed ice cover]
-
A.
isGlacialLake
Indicates that a body of water is classified as a glacial lake, formed by the action or presence of glaciers.
-
B.
glacierType
Indicates the specific classification or category of a glacier based on its form, dynamics, or setting.
-
C.
glaciationCharacteristic
chosen
Indicates that one entity is a characteristic, feature, or property associated with the process or effects of glaciation of another entity.
-
D.
glaciologicalZone
Indicates the specific glaciological region or zone within or around a glacier in which a process, condition, or classification applies.
-
E.
glaciologicalRegion
Indicates the geographic area or zone defined and studied in relation to glaciers and glacial processes.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:05 a.m.