Triple

T4889012
Position Surface form Disambiguated ID Type / Status
Subject Lansdowne, Virginia E109510 entity
Predicate nearbyCommunity P4647 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: [Lansdowne, Virginia, nearbyCommunity, Ashburn, Virginia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashburn, Virginia
Context triple: [Lansdowne, Virginia, nearbyCommunity, 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_69bd440f71348190b99938e59fb7f9a1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6e06a81881908734dbdc350a2039 completed March 20, 2026, 3:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69bfbd5d67c881909b57ead8968a840b completed March 22, 2026, 9:58 a.m.
Created at: March 20, 2026, 1:28 p.m.