Triple
T35411778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okanogan Lobe |
E1023530
|
entity |
| Predicate | meltwaterProduced |
P50125
|
FINISHED |
| Object | glacial meltwater streams |
—
|
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: glacial meltwater streams | Statement: [Okanogan Lobe, meltwaterProduced, glacial meltwater streams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meltwaterProduced Context triple: [Okanogan Lobe, meltwaterProduced, glacial meltwater streams]
-
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.
canMelt
Indicates that one entity has the capability to melt another entity or substance under appropriate conditions.
-
C.
producesWaterMass
Indicates that one entity generates or yields a quantity of water as a result of its action or process.
-
D.
glacierFlowRate
Indicates the rate at which a glacier moves or flows over a given distance in a specified time.
-
E.
lakeOutflow
Indicates that a lake serves as the source from which water flows out into another body of water or drainage system.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f795672b40819087ccce744e044124 |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.