Triple
T29874354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parleys Creek |
E758678
|
entity |
| Predicate | watershedServes |
P17416
|
FINISHED |
| Object | Salt Lake Valley |
E123689
|
NE 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: Salt Lake Valley | Statement: [Parleys Creek, watershedServes, Salt Lake Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watershedServes Context triple: [Parleys Creek, watershedServes, Salt Lake Valley]
-
A.
basinServed
Indicates that a particular basin is supplied, drained, or otherwise functionally supported by another entity (such as a river, watershed, or infrastructure system).
-
B.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
C.
watershedName
Indicates the name assigned to the watershed with which an entity is associated.
-
D.
hasWatershed
chosen
Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
-
E.
watershedType
Indicates the classification or category of a watershed associated with an entity (e.g., by hydrologic, ecological, or management type).
- F. None of above.
Provenance (4 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2721e1ce80819081aa7b21ff16f823 |
completed | June 8, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 29, 2026, 5:55 p.m.