Triple
T18262659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tustumena Glacier |
E437400
|
entity |
| Predicate | hasMeltwaterDestination |
P49019
|
FINISHED |
| Object | Tustumena Lake |
—
|
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: Tustumena Lake | Statement: [Tustumena Glacier, hasMeltwaterDestination, Tustumena Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeltwaterDestination Context triple: [Tustumena Glacier, hasMeltwaterDestination, Tustumena Lake]
-
A.
hasMeltwaterContributionTo
Indicates that one entity contributes meltwater (from melting ice or snow) to another entity, such as a water body or hydrological system.
-
B.
receivesMeltwaterFrom
chosen
Indicates that one entity obtains meltwater that flows or is transferred from another entity.
-
C.
hasGlacierOutlet
Indicates that a glacier has a specific outlet feature or location through which its ice or meltwater flows or exits.
-
D.
hasWatershed
Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
-
E.
hasWatershedWith
Indicates that two geographic areas share or are associated with the same watershed or drainage basin.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff77882c81909774aefc57ccca3e |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.