Triple
T27484446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naches River |
E693695
|
entity |
| Predicate | hasDamOnTributary |
P32893
|
FINISHED |
| Object | Tieton Dam |
—
|
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: Tieton Dam | Statement: [Naches River, hasDamOnTributary, Tieton Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDamOnTributary Context triple: [Naches River, hasDamOnTributary, Tieton Dam]
-
A.
isTributaryDamOf
Indicates that a dam is constructed on and regulates the flow of a tributary river or stream relative to a main watercourse.
-
B.
hasTributaryRelationsWith
Indicates that one entity maintains a tributary relationship with another, typically involving regular payments or offerings in exchange for protection, favor, or acknowledgment of superiority.
-
C.
isHeadwaterTributaryOf
Indicates that one watercourse is a source or upstream tributary that feeds into another watercourse.
-
D.
upstreamDam
Indicates that one entity is located or positioned upstream of another entity in relation to a dam, typically affecting or influenced by the dam’s presence or operation.
-
E.
watercourseHasDam
chosen
Indicates that a watercourse (such as a river or stream) has a dam constructed on or across it.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 1:01 p.m.