Triple

T20944130
Position Surface form Disambiguated ID Type / Status
Subject Route 28 (Sully Road) E515800 entity
Predicate alsoKnownAs P39 FINISHED
Object VA 28 NE NERFINISHED

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: VA 28 | Statement: [Route 28 (Sully Road), alsoKnownAs, VA 28]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: VA 28
Context triple: [Route 28 (Sully Road), alsoKnownAs, VA 28]
  • A. VA 28 chosen
    VA 28 is a major north–south state highway in Northern Virginia that serves as a key commuter and freight corridor connecting Dulles International Airport and surrounding suburbs to other regional routes.
  • B. VA 230
    VA 230 is a primary state highway in Virginia that connects U.S. Route 29 near Madison to U.S. Route 33 near Stanardsville, serving rural communities in Madison and Greene counties.
  • C. VA 234
    VA 234 is a primary state highway in Virginia that connects the Manassas area with Interstate 95 and other major routes in Northern Virginia.
  • D. VA 3
    VA 3 is a primary state highway in Virginia that connects the Fredericksburg area with the Northern Neck region, serving as a key east–west route.
  • E. VA 243
    VA 243 is a short primary state highway in Fairfax County, Virginia, connecting Vienna to the surrounding road network near the Vienna/Fairfax–GMU Metro station.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4fc13408190b06868df03c5c29b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fad705e481909da0098d7c73cd02 completed April 21, 2026, 4:19 a.m.
Created at: April 16, 2026, 12:52 p.m.