Triple
T10983777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santiam Pass |
E259573
|
entity |
| Predicate | isMajorTransportationRoute |
P87781
|
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: [Santiam Pass, isMajorTransportationRoute, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorTransportationRoute Context triple: [Santiam Pass, isMajorTransportationRoute, yes]
-
A.
hasMajorTransportationRole
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
-
B.
isMajorTransportLink
chosen
Indicates that something serves as a primary or highly significant route or connection for transporting people or goods between places.
-
C.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
D.
isMajorTransportLinkIn
Indicates that a transport route or connection serves as a primary or significant transportation link within a specified area or region.
-
E.
hasMajorRouteType
Indicates that an entity is associated with a primary classification of transportation route (such as highway, rail line, or other major route type).
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772ec55fc81909b2b15f2493dddc6 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.