Triple

T6522153
Position Surface form Disambiguated ID Type / Status
Subject Grimsby Town F.C. E151209 entity
Predicate location P40 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: [Grimsby Town F.C., location, Grimsby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Grimsby
Context triple: [Grimsby Town F.C., location, Grimsby]
  • A. Grimsby
    Grimsby is a town in Ontario, Canada, located on the southern shore of Lake Ontario between Hamilton and St. Catharines.
  • B. 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.
  • C. Cleethorpes
    Cleethorpes is a seaside resort town on the east coast of England, known for its sandy beaches, promenade, and traditional British holiday attractions.
  • D. 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.
  • 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_69c687f522748190b3058405553cdabd completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6ad95c2c88190b800aaaa73f99210 completed March 27, 2026, 4:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6d5204e78819082bf991c2ece09df completed March 27, 2026, 7:06 p.m.
Created at: March 27, 2026, 1:45 p.m.