Triple
T27767275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puyallup Glacier |
E701634
|
entity |
| Predicate | contributesMeltwaterTo |
P50125
|
FINISHED |
| Object | Puyallup River system |
—
|
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: Puyallup River system | Statement: [Puyallup Glacier, contributesMeltwaterTo, Puyallup River system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contributesMeltwaterTo Context triple: [Puyallup Glacier, contributesMeltwaterTo, Puyallup River system]
-
A.
hasMeltwaterContributionTo
chosen
Indicates that one entity contributes meltwater (from melting ice or snow) to another entity, such as a water body or hydrological system.
-
B.
receivesMeltwaterFrom
Indicates that one entity obtains meltwater that flows or is transferred from another entity.
-
C.
contributesRunoffTo
Indicates that one entity generates surface or subsurface water flow that is directed into and increases the runoff of another entity.
-
D.
producesWaterMass
Indicates that one entity generates or yields a quantity of water as a result of its action or process.
-
E.
glacierConfluenceOf
Indicates that one glacier joins or merges into another glacier at a specific location.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 4:32 p.m.