Triple

T4330663
Position Surface form Disambiguated ID Type / Status
Subject Killingholme E96739 entity
Predicate hasNearby P350 FINISHED
Object Grimsby E141371 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: Grimsby | Statement: [Killingholme, hasNearby, Grimsby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Grimsby
Context triple: [Killingholme, hasNearby, Grimsby]
  • A. Grimsby chosen
    Grimsby is a large coastal town and historic fishing port in North East Lincolnshire, England, known for its maritime heritage and seafood industry.
  • B. Cleethorpes
    Cleethorpes is a seaside resort town on the east coast of England, known for its sandy beaches, promenade, and traditional British holiday attractions.
  • C. Morecambe
    Morecambe is a seaside resort town on the coast of Morecambe Bay in north-west England, known for its promenade, beaches, and views across the bay to the Lake District.
  • D. Hull
    Hull is a small coastal town in eastern Massachusetts known for its beaches and seaside community on a narrow peninsula.
  • 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_69b34542fd908190b11b08faad8decfd completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3514c39748190900e13e70ed8848c completed March 12, 2026, 11:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b66b29cbe4819083788fe6e3e8ba3b completed March 15, 2026, 8:17 a.m.
Created at: March 12, 2026, 11:13 p.m.