Triple
T25989353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tooma River |
E646299
|
entity |
| Predicate | hasSnowmeltSource |
P50125
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tooma River, hasSnowmeltSource, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSnowmeltSource Context triple: [Tooma River, hasSnowmeltSource, true]
-
A.
hasSnowAndIceSource
Indicates that something derives its origin, supply, or input from a source consisting of snow and ice.
-
B.
hasMeltwaterContributionTo
chosen
Indicates that one entity contributes meltwater (from melting ice or snow) to another entity, such as a water body or hydrological system.
-
C.
primarySnowSource
Indicates that one entity serves as the main origin or contributor of snow for another entity or location.
-
D.
hasHydrologicalSource
Indicates that one entity serves as the hydrological origin or water source (e.g., spring, glacier, lake) from which another water body or hydrological feature arises or is fed.
-
E.
isGlaciallyFed
Indicates that something (typically a body of water) receives its primary input or supply from melting glacial ice.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605469f7881909fb9d981d79def18 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:55 a.m.