Triple

T4536087
Position Surface form Disambiguated ID Type / Status
Subject Virginia State Route 267 E107411 entity
Predicate connects P390 FINISHED
Object Leesburg, Virginia E30919 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: Leesburg, Virginia | Statement: [Virginia State Route 267, connects, Leesburg, Virginia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leesburg, Virginia
Context triple: [Virginia State Route 267, connects, Leesburg, Virginia]
  • A. Leesburg chosen
    Leesburg is a historic town in Loudoun County that serves as a suburban hub of Northern Virginia near Washington, D.C.
  • B. 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.
  • C. Reston
    Reston is a planned community in Fairfax County, Virginia, known for its pioneering mixed-use design, extensive green spaces, and vibrant residential and commercial centers.
  • D. Reston
    Reston is a small rural village in the Scottish Borders region of southeastern Scotland.
  • E. Nokesville, Virginia
    Nokesville, Virginia is a small rural community in Northern Virginia known for its farmland, equestrian activities, and quiet residential character.
  • 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_69bf88d99da08190996996079b947498 completed March 22, 2026, 6:14 a.m.
Created at: March 20, 2026, 1:04 p.m.