Triple
T36730616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spillway Lake |
E907322
|
entity |
| Predicate | sourceGlacier |
P25271
|
FINISHED |
| Object | Ngozumpa Glacier |
—
|
NE NERFINISHED |
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: Ngozumpa Glacier | Statement: [Spillway Lake, sourceGlacier, Ngozumpa Glacier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceGlacier Context triple: [Spillway Lake, sourceGlacier, Ngozumpa Glacier]
-
A.
glacierCode
Indicates a classification or identifier assigned to a glacier, linking it to a specific code used for cataloging or reference.
-
B.
feedsGlacier
chosen
Indicates that one entity supplies water, ice, or material that contributes to the growth or sustenance of a glacier.
-
C.
formsGlacierSystemWith
Indicates that one glacier or glacial feature combines or interacts with another to form a connected or integrated glacier system.
-
D.
glacierContext
Indicates that something occurs within, is associated with, or is defined by the environmental, geological, or situational context of a glacier.
-
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.
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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:12 p.m.