Triple
T30221455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bingen, Washington |
E768353
|
entity |
| Predicate | crossRiverCity |
P73938
|
FINISHED |
| Object | Hood River, Oregon |
—
|
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: Hood River, Oregon | Statement: [Bingen, Washington, crossRiverCity, Hood River, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossRiverCity Context triple: [Bingen, Washington, crossRiverCity, Hood River, Oregon]
-
A.
crossRiverLink
chosen
Indicates a connection or route that enables passage across a river between two locations.
-
B.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
C.
cityOnBothBanks
Indicates that a city is situated so that it occupies or extends across both banks of a river.
-
D.
capitalCityOnRiver
Indicates that a capital city is located on and directly adjacent to a particular river.
-
E.
riverSeparatingCity
Indicates that a river runs between and divides parts of a city or separates one city from another.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 29, 2026, 7:35 p.m.