Triple

T4536112
Position Surface form Disambiguated ID Type / Status
Subject Virginia State Route 267 E107411 entity
Predicate serves P98 FINISHED
Object Ashburn, Virginia E30324 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: Ashburn, Virginia | Statement: [Virginia State Route 267, serves, Ashburn, Virginia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashburn, Virginia
Context triple: [Virginia State Route 267, serves, Ashburn, Virginia]
  • A. Ashburn chosen
    Ashburn is a rapidly growing suburban community in Loudoun County, Virginia, known for its major data centers, tech industry presence, and planned residential neighborhoods.
  • B. Ashburn
    Ashburn is a residential neighborhood located on the Southwest Side of Chicago, Illinois.
  • C. Falls Church
    Falls Church is an independent city in Northern Virginia, near Washington, D.C., known for its small size, historic character, and suburban residential communities.
  • D. Leesburg
    Leesburg is a historic town in Loudoun County that serves as a suburban hub of Northern Virginia near Washington, D.C.
  • E. Fairfax, Virginia
    Fairfax, Virginia is an independent city in Northern Virginia that serves as a major suburban community within the Washington, D.C. metropolitan area.
  • 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_69bd43f922788190b7edfa294e39b178 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd57b634b08190845d04213cf8d5b9 completed March 20, 2026, 2:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf9ad2f8e48190aac71e657a9e1197 completed March 22, 2026, 7:31 a.m.
Created at: March 20, 2026, 1:04 p.m.