Triple
T33523593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Condon, Oregon |
E858575
|
entity |
| Predicate | nearestLargeRiverBasin |
P72732
|
FINISHED |
| Object | Columbia River Basin |
—
|
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: Columbia River Basin | Statement: [Condon, Oregon, nearestLargeRiverBasin, Columbia River Basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestLargeRiverBasin Context triple: [Condon, Oregon, nearestLargeRiverBasin, Columbia River Basin]
-
A.
associatedRiverBasin
chosen
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
-
B.
basinPartOf
Indicates that one basin is a component or subdivision of a larger basin or basin system.
-
C.
closelyAssociatedRiver
Indicates a river that is geographically or functionally closely connected to the subject, such as flowing nearby, through, or otherwise strongly linked to it.
-
D.
countryDownstreamBasin
Indicates that one country lies within the downstream portion of a river basin relative to another country or reference point.
-
E.
basinFor
Indicates that something serves as a basin or receptacle specifically intended for collecting, holding, or draining 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 1:39 a.m.