Triple
T6430261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khumbu Icefall |
E128160
|
entity |
| Predicate | glacierFlowRate |
P70851
|
FINISHED |
| Object | up to about 0.9 meters per day |
—
|
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: up to about 0.9 meters per day | Statement: [Khumbu Icefall, glacierFlowRate, up to about 0.9 meters per day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glacierFlowRate Context triple: [Khumbu Icefall, glacierFlowRate, up to about 0.9 meters per day]
-
A.
glacierType
Indicates the specific classification or category of a glacier based on its form, dynamics, or setting.
-
B.
notableGlacier
Indicates that the subject is a glacier recognized for its particular significance, prominence, or noteworthiness.
-
C.
numberOfGlaciers
Indicates the quantity of glaciers associated with a given entity.
-
D.
glaciersStatus
Indicates the current condition or state of glaciers, such as their size, stability, or rate of change.
-
E.
glaciologicalMonitoring
Indicates the systematic observation and measurement of glaciers and related ice features to track their physical changes and dynamics over time.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693b872c819082a7d0e257018831 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c062d290448190a2183158ef75d129 |
completed | March 22, 2026, 9:44 p.m. |
Created at: March 22, 2026, 4:44 p.m.