Triple

T12141563
Position Surface form Disambiguated ID Type / Status
Subject State Route 520 E289194 entity
Predicate connects P390 FINISHED
Object SR 202 in Redmond E456452 NE 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: SR 202 in Redmond | Statement: [State Route 520, connects, SR 202 in Redmond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SR 202 in Redmond
Context triple: [State Route 520, connects, SR 202 in Redmond]
  • A. SR 202 chosen
    SR 202 is a state highway loop route commonly referred to as Loop 202.
  • B. SR 20
    SR 20 is a state highway in Georgia that runs across the northern part of the state, connecting several suburbs and communities around the Atlanta metropolitan area.
  • C. SR 20
    SR 20 is a major east–west state highway in Northern California that connects the Pacific Coast near Fort Bragg to the Sacramento Valley and the Sierra Nevada region.
  • D. SR 120
    SR 120 is a California state highway best known for providing a key east–west route through Yosemite National Park and over the Sierra Nevada.
  • E. SR 2
    SR 2 is a state highway in the Florida Panhandle that runs near the Alabama border, serving as an east–west route through rural communities.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6ab4c6710819097a9d228382dde43 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d915a9838081909622cc14df2a2582 completed April 10, 2026, 3:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f692ee048190ab42c92296fd28fb completed May 2, 2026, 1:05 p.m.
Created at: April 8, 2026, 9:49 p.m.