Triple
T20767319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington State Route 20 |
E511130
|
entity |
| Predicate | isKeyEastWestCorridor |
P121975
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Washington State Route 20, isKeyEastWestCorridor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyEastWestCorridor Context triple: [Washington State Route 20, isKeyEastWestCorridor, true]
-
A.
isOnEastWestTrunkLine
Indicates that something is located on, or directly aligned with, a primary east–west transportation or utility trunk line.
-
B.
hasEastExit
Indicates that an entity has an exit or passage leading to the east.
-
C.
isCoastalCorridor
Indicates that a region or area functions as a continuous coastal passageway connecting different coastal locations.
-
D.
hasEastboundService
Indicates that a location, route, or facility is served by transportation services traveling in an eastbound direction.
-
E.
isStrategicCorridor
chosen
Indicates that a route, passage, or area serves as a critical pathway for movement, access, or control, giving it significant strategic importance.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24df58c8190b37398353ce4bf24 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:36 p.m.