Triple

T14754711
Position Surface form Disambiguated ID Type / Status
Subject Holderness coastline E346700 entity
Predicate nearbyTown P3883 FINISHED
Object Bridlington E282446 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: Bridlington | Statement: [Holderness coastline, nearbyTown, Bridlington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bridlington
Context triple: [Holderness coastline, nearbyTown, Bridlington]
  • A. Bridlington chosen
    Bridlington is a coastal town and popular seaside resort on the North Sea in the East Riding of Yorkshire, England.
  • B. Bridlington
    Bridlington is the later name of the historical settlement originally known as Burlington in the former Province of New Jersey.
  • C. Bridlington Bay
    Bridlington Bay is a shallow, sweeping bay on England’s East Yorkshire coast, known for its sandy beaches, seaside tourism, and role as a sheltered fishing and sailing area.
  • D. Southfleet
    Southfleet is a small rural village and civil parish in north-west Kent, England, known for its historic church and traditional countryside setting.
  • E. Barton-on-Humber
    Barton-on-Humber is a small historic town in North Lincolnshire, England, situated on the south bank of the Humber Estuary.
  • 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_69d822e8896c819091169882f9b20486 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec7d59df08190a86da5048358bd6e completed April 14, 2026, 11:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe24afff788190ab4925ead7ce90d2 completed May 8, 2026, 6 p.m.
Created at: April 10, 2026, 1:30 a.m.