Triple
T10168979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Route 35 |
E235279
|
entity |
| Predicate | mountainPassRoad |
P51040
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
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: yes | Statement: [Oregon Route 35, mountainPassRoad, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainPassRoad Context triple: [Oregon Route 35, mountainPassRoad, yes]
-
A.
crossesMountainPass
chosen
Indicates that an entity traverses from one side of a mountain range to another via a defined mountain pass.
-
B.
hasMountainPassNearby
Indicates that a mountain pass is located in close proximity to the referenced place or feature.
-
C.
highestRoadPassIn
Indicates that a location contains the highest-elevation road pass within a specified area or region.
-
D.
southMountainSegmentCompleted
Indicates that the construction or development of the south mountain segment has been fully completed.
-
E.
crossesMountainRange
Indicates that one entity traverses from one side of a mountain range to the other, passing through or over 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec9ba56481908b5265aea8ea8cbe |
completed | April 2, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.