Triple
T8158732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Route 18 |
E190518
|
entity |
| Predicate | hasFreewaySegments |
P80869
|
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 18, hasFreewaySegments, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFreewaySegments Context triple: [Oregon Route 18, hasFreewaySegments, yes]
-
A.
isFreeway
Indicates that a given road segment functions as a freeway, typically designed for high-speed, limited-access vehicular traffic.
-
B.
hasExpresswaySection
Indicates that an entity includes, contains, or is associated with a specific section or segment of an expressway.
-
C.
hasExpressLanes
Indicates that a roadway or transportation facility includes designated express lanes for faster or prioritized travel.
-
D.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
E.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
- F. None of above. chosen
Provenance (4 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb455213f08190a4327a2116c7381f |
completed | March 31, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb39ba412881908a053e88f29a9588 |
completed | March 31, 2026, 3:04 a.m. |
Created at: March 30, 2026, 5:38 p.m.