Triple

T4096668
Position Surface form Disambiguated ID Type / Status
Subject Teesside Crown Court E87837 entity
Predicate regionServed P82 FINISHED
Object Hartlepool E115176 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: Hartlepool | Statement: [Teesside Crown Court, regionServed, Hartlepool]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hartlepool
Context triple: [Teesside Crown Court, regionServed, Hartlepool]
  • A. Hartlepool chosen
    Hartlepool is a coastal town in County Durham, England, known historically for its shipbuilding and maritime heritage.
  • B. Tynemouth
    Tynemouth is a coastal town in Tyne and Wear, England, known for its historic priory and castle overlooking long sandy beaches at the mouth of the River Tyne.
  • C. Hull
    Hull is a small coastal town in eastern Massachusetts known for its beaches and seaside community on a narrow peninsula.
  • D. 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.
  • E. 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.
  • 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_69aed94564cc8190a9c1457daedb6e7f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefcdef11081908c626a89f2c0e121 completed March 9, 2026, 5:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69b57f1d1ab081909b7999e8feede458 completed March 14, 2026, 3:30 p.m.
Created at: March 9, 2026, 3:40 p.m.