Triple
T15053896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 405 (Washington) |
E379436
|
entity |
| Predicate | expressTollLanesLocation |
P19598
|
FINISHED |
| Object | between Bellevue and Lynnwood |
—
|
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: between Bellevue and Lynnwood | Statement: [Interstate 405 (Washington), expressTollLanesLocation, between Bellevue and Lynnwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expressTollLanesLocation Context triple: [Interstate 405 (Washington), expressTollLanesLocation, between Bellevue and Lynnwood]
-
A.
tollRoadOf
Indicates that a road segment is a toll road belonging to or associated with a particular roadway, route, or transportation network.
-
B.
tollRoadServiceAreaFor
Indicates that a toll road service area is designated to serve or is associated with a specific toll road segment or route.
-
C.
tollFacilityName
Indicates the name assigned to a toll facility where tolls are collected.
-
D.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
E.
hasExpressLanes
chosen
Indicates that a roadway or transportation facility includes designated express lanes for faster or prioritized travel.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda92091c81909180f486edf01405 |
completed | April 15, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:01 a.m.