Triple

T14171341
Position Surface form Disambiguated ID Type / Status
Subject Burlington E351213 entity
Predicate hasPort P35 FINISHED
Object Burlington Harbor E372290 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 Harbor | Statement: [Burlington, hasPort, Burlington Harbor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burlington Harbor
Context triple: [Burlington, hasPort, Burlington Harbor]
  • A. Burlington Harbor chosen
    Burlington Harbor is a waterfront harbor on Lake Champlain that serves as the primary marina and recreational boating hub for Burlington, Vermont.
  • B. Centerville Harbor
    Centerville Harbor is a small coastal inlet and boating area on Cape Cod in Barnstable, Massachusetts.
  • C. Saquatucket Harbor
    Saquatucket Harbor is a marina and harbor facility in Harwich, Massachusetts, serving as a key hub for recreational boating and ferry service to nearby Cape Cod destinations.
  • D. Shelburne Bay
    Shelburne Bay is a scenic inlet of Lake Champlain in Vermont known for its boating, fishing, and wildlife viewing opportunities.
  • E. Burlington Bay
    Burlington Bay is the historic name for Hamilton Harbour, a natural bay at the western end of Lake Ontario in Ontario, Canada.
  • 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_69d8278834a08190b0f1784e58d7b99c completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61b5dcbc8190b0cfcce5e6c6d582 completed April 14, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd324772e4819092aef7826b39b144 completed May 8, 2026, 12:45 a.m.
Created at: April 10, 2026, 1:01 a.m.