Triple

T9516315
Position Surface form Disambiguated ID Type / Status
Subject Northwest Washington E229533 entity
Predicate includesCity P3207 FINISHED
Object Burlington E344391 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: Burlington | Statement: [Northwest Washington, includesCity, Burlington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burlington
Context triple: [Northwest Washington, includesCity, Burlington]
  • A. Burlington
    Burlington is a suburban town in Massachusetts known for its proximity to Boston and its mix of residential neighborhoods, office parks, and retail centers.
  • B. Burlington
    Burlington is a historic city in present-day New Jersey that once served as the colonial capital of the Province of New Jersey.
  • C. Burlington
    Burlington is a mid-sized city in southern Ontario, Canada, located on the shores of Lake Ontario between Toronto and Hamilton.
  • D. Burlington chosen
    Burlington is a small city in northwestern Washington State known as a commercial hub for the surrounding Skagit Valley region.
  • E. Burlington
    Burlington is a small city in southeastern Wisconsin known for its historic downtown, chocolate festival, and role as a local commercial and community hub.
  • 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_69ca84777560819084cddd999badc1aa completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd987eefec8190b0db1928776bf02b completed April 1, 2026, 10:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1526fbad8819099dfae3b7226898b completed April 4, 2026, 6:03 p.m.
Created at: March 30, 2026, 7:58 p.m.