Triple

T2851485
Position Surface form Disambiguated ID Type / Status
Subject Chicago Lawn E63100 entity
Predicate hasBorder P224 FINISHED
Object Ashburn E407579 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 | Statement: [Chicago Lawn, hasBorder, Ashburn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashburn
Context triple: [Chicago Lawn, hasBorder, Ashburn]
  • A. Ashburn
    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 chosen
    Ashburn is a residential neighborhood located on the Southwest Side of Chicago, Illinois.
  • C. Leesburg
    Leesburg is a historic town in Loudoun County that serves as a suburban hub of Northern Virginia near Washington, D.C.
  • D. Centreville
    Centreville is a suburban community in Fairfax County, Virginia, known for its residential neighborhoods and proximity to Washington, D.C.
  • E. 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.
  • 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_69ab4c407c408190857d25e027155ce9 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdf5ca2648190bd32c6ec4b0dd3b6 completed March 7, 2026, 8:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69b5c6d1e3b08190beff7f113dec8b1c completed March 14, 2026, 8:36 p.m.
Created at: March 6, 2026, 10:02 p.m.