Triple

T20597091
Position Surface form Disambiguated ID Type / Status
Subject BNSF Bellingham Subdivision E506077 entity
Predicate servesCommunity P82 FINISHED
Object Burlington NE NERFINISHED

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: [BNSF Bellingham Subdivision, servesCommunity, Burlington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burlington
Context triple: [BNSF Bellingham Subdivision, servesCommunity, Burlington]
  • A. Burlington
    Burlington is a historic city in present-day New Jersey that once served as the colonial capital of the Province of New Jersey.
  • B. Burlington chosen
    Burlington is a mid-sized city in southern Ontario, Canada, located on the shores of Lake Ontario between Toronto and Hamilton.
  • C. Burlington
    Burlington is a city in North Carolina known historically as a railroad and textile manufacturing hub in the Piedmont region of the state.
  • D. Burlington
    Burlington is a city in northwestern Vermont on the shores of Lake Champlain, known as the state’s largest city and a regional cultural and economic center.
  • E. Burlington
    Burlington is a small town that serves as a local community and commercial center along 3rd Avenue.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4ba6ae88190af871e1f9522c704 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6aa1d15b08190a720fc7cefbf333e completed April 20, 2026, 10:35 p.m.
Created at: April 16, 2026, 11:40 a.m.