Triple
T28983483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon–Idaho border near Boise |
E734613
|
entity |
| Predicate | adjacentCountyOnOregonSide |
P6346
|
FINISHED |
| Object | Malheur County, 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: Malheur County, Oregon | Statement: [Oregon–Idaho border near Boise, adjacentCountyOnOregonSide, Malheur County, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentCountyOnOregonSide Context triple: [Oregon–Idaho border near Boise, adjacentCountyOnOregonSide, Malheur County, Oregon]
-
A.
hasNearbyCounty
Indicates that one county is geographically close to or directly adjacent to another county.
-
B.
adjacentToCounty
chosen
Indicates that one county directly borders or touches another county geographically.
-
C.
isCornerCountyOf
Indicates that a county lies at or near the corner where two or more larger administrative regions (such as states or districts) meet.
-
D.
locatedNorthwestOf
Indicates that one entity is positioned to the northwest of another entity in space or geography.
-
E.
hasNearbyCountyBorder
Indicates that the borders of two counties are geographically close to each other, though not necessarily directly adjacent.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 28, 2026, 9:12 a.m.