Triple

T19910925
Position Surface form Disambiguated ID Type / Status
Subject Community Field E478543 entity
Predicate city P40 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: [Community Field, city, Burlington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burlington
Context triple: [Community Field, city, 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 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 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 (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_69d8e520682081909892916424699bd5 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6598f31c481908a5a1d9a5656f698 completed April 20, 2026, 4:51 p.m.
Created at: April 10, 2026, 1:53 p.m.