Triple

T4070986
Position Surface form Disambiguated ID Type / Status
Subject Long Wharf, Boston E86644 entity
Predicate ferryServiceTo P1737 FINISHED
Object Hull E161885 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: Hull | Statement: [Long Wharf, Boston, ferryServiceTo, Hull]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hull
Context triple: [Long Wharf, Boston, ferryServiceTo, Hull]
  • A. Hull chosen
    Hull is a small coastal town in eastern Massachusetts known for its beaches and seaside community on a narrow peninsula.
  • B. Hull
    Hull, formally known as Kingston upon Hull, is a port city in East Yorkshire, England, noted for its maritime heritage and role as a major North Sea trading hub.
  • C. Hull
    Hull is a former city in western Quebec, Canada, that once stood on the north shore of the Ottawa River and is now part of the amalgamated city of Gatineau.
  • D. Hull
    Hull is a common English surname borne by various notable individuals across politics, sports, and the arts.
  • E. Hartlepool
    Hartlepool is a coastal town in County Durham, England, known historically for its shipbuilding and maritime heritage.
  • 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_69aed93ebe448190a1f1686e28740ac9 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af019af25481909e9f1d171356f3e8 completed March 9, 2026, 5:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69b562b6eb708190a7f60192d8df9a27 completed March 14, 2026, 1:29 p.m.
Created at: March 9, 2026, 3:38 p.m.