Triple
T8664163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoshone Falls |
E205622
|
entity |
| Predicate | flowDependentOn |
P51098
|
FINISHED |
| Object | Snake River streamflow |
—
|
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: Snake River streamflow | Statement: [Shoshone Falls, flowDependentOn, Snake River streamflow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowDependentOn Context triple: [Shoshone Falls, flowDependentOn, Snake River streamflow]
-
A.
flowsTo
Indicates that something moves or is directed from one location or entity toward and into another, typically in a continuous or channel-like manner.
-
B.
riverDependency
chosen
Indicates a relationship where one entity relies on or is significantly influenced by a river for its existence, function, or sustainability.
-
C.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
D.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
E.
dependency
Indicates that one entity relies on, is conditioned by, or cannot function or exist properly without another entity.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc489f7edc8190bde1b4dc09249207 |
completed | March 31, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:30 p.m.