Triple

T11263836
Position Surface form Disambiguated ID Type / Status
Subject State Route 520 E266630 entity
Predicate providesRegionalAccessBetween P24718 FINISHED
Object Seattle and Bellevue 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: Seattle and Bellevue | Statement: [State Route 520, providesRegionalAccessBetween, Seattle and Bellevue]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: providesRegionalAccessBetween
Context triple: [State Route 520, providesRegionalAccessBetween, Seattle and Bellevue]
  • A. servesRegionAcrossFrom
    Indicates that a service or entity operates in a region that is geographically located directly across from another specified region.
  • B. accessesRegion
    Indicates that one entity reaches, uses, or interacts with a specific geographic or logical region.
  • C. connectsRegions chosen
    Indicates a relationship where one entity links or joins two or more distinct regions, enabling passage, interaction, or continuity between them.
  • D. servesAsGatewayTo
    Indicates that one entity functions as an entry point, access route, or intermediary channel that enables reaching or connecting to another entity.
  • E. isRegionalCrossroads
    Indicates that a place serves as a key junction where multiple regional routes, networks, or areas intersect and connect.
  • 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_69d6aac7953c8190b82caf9d7640fdf9 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e94d56048190bf808e1bc2188714 completed April 9, 2026, 6 p.m.
PD Predicate disambiguation batch_69d7879bc56c8190b2e8d2193f29de05 completed April 9, 2026, 11:03 a.m.
Created at: April 8, 2026, 9:31 p.m.