Triple

T17041886
Position Surface form Disambiguated ID Type / Status
Subject Port of Halifax E413463 entity
Predicate near P350 FINISHED
Object Downtown Halifax E18498 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: Downtown Halifax | Statement: [Port of Halifax, near, Downtown Halifax]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Downtown Halifax
Context triple: [Port of Halifax, near, Downtown Halifax]
  • A. Halifax
    Halifax is a historic industrial town in West Yorkshire, England, known for its textile heritage and distinctive Victorian architecture.
  • B. Halifax
    Halifax is a major UK retail bank known for offering personal banking, mortgages, and savings products.
  • C. Halifax chosen
    Halifax is the capital city of the Canadian province of Nova Scotia, known as a major Atlantic port and regional economic and cultural center.
  • D. Halifax
    Halifax was a British four‑engined heavy bomber aircraft widely used by the Royal Air Force during World War II.
  • E. Halifax
    Halifax is a small town in Plymouth County, Massachusetts, known for its residential character and proximity to numerous lakes and conservation areas.
  • 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_69d886cd18288190b006abab23f811b7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d8f771608190b596138ddec118c6 completed April 18, 2026, 7:18 p.m.
NED1 Entity disambiguation (via context triple) batch_6a01233a7e44819096f71f5007b4450f completed May 11, 2026, 12:30 a.m.
Created at: April 10, 2026, 5:33 a.m.