Triple
T11401905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VA 7 |
E270128
|
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: [VA 7, serves, Ashburn, Virginia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashburn, Virginia Context triple: [VA 7, 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e624600e0081909cc6f53c05a34efb |
completed | April 20, 2026, 1:04 p.m. |
Created at: April 8, 2026, 9:34 p.m.