Triple
T20282436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jungfraufirn |
E503182
|
entity |
| Predicate | glaciologicalZone |
P139533
|
FINISHED |
| Object | accumulation zone |
—
|
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: accumulation zone | Statement: [Jungfraufirn, glaciologicalZone, accumulation zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glaciologicalZone Context triple: [Jungfraufirn, glaciologicalZone, accumulation zone]
-
A.
glaciologicalRegion
Indicates the geographic area or zone defined and studied in relation to glaciers and glacial processes.
-
B.
glaciologicalRole
Indicates the specific function, activity, or responsibility an entity has within the study or processes of glaciers and ice.
-
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.
glacierType
Indicates the specific classification or category of a glacier based on its form, dynamics, or setting.
-
E.
glacierSystem
Indicates a relationship where entities participate in or belong to the same interconnected system of glaciers and related glacial components.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6768f86448190842389a98b93a918 |
completed | April 20, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 10:40 a.m.