Triple
T26879628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deschutes River (Washington) |
E676853
|
entity |
| Predicate | hasCityAlongCourse |
P143970
|
FINISHED |
| Object | Tumwater, Washington |
—
|
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: Tumwater, Washington | Statement: [Deschutes River (Washington), hasCityAlongCourse, Tumwater, Washington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityAlongCourse Context triple: [Deschutes River (Washington), hasCityAlongCourse, Tumwater, Washington]
-
A.
hasMunicipalityAlongCourse
chosen
Indicates that a watercourse passes through or alongside a given municipality along its path.
-
B.
hasMajorCityOnRoute
Indicates that a major city lies along, or is directly served by, a specified route or path between locations.
-
C.
passesNearCity
Indicates that the path, route, or trajectory of one entity goes close to, but not necessarily through, a specified city.
-
D.
passesCity
Indicates that a route, path, or journey goes through or traverses a particular city as part of its course.
-
E.
hasNotableFeatureAlongCourse
Indicates that something possesses a notable or distinguishing feature at some point along its course or path.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 5:38 a.m.