Triple

T1823406
Position Surface form Disambiguated ID Type / Status
Subject Morecambe E40592 entity
Predicate postalTown P2711 FINISHED
Object MORECAMBE E40592 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: MORECAMBE | Statement: [Morecambe, postalTown, MORECAMBE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MORECAMBE
Context triple: [Morecambe, postalTown, MORECAMBE]
  • A. Morecambe chosen
    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.
  • B. Grimsby
    Grimsby is a large coastal town and historic fishing port in North East Lincolnshire, England, known for its maritime heritage and seafood industry.
  • C. Bury
    Bury is a town in North West England known for its traditional market, historic textile industry roots, and preserved East Lancashire Railway.
  • D. Scunthorpe
    Scunthorpe is an industrial town in North Lincolnshire, England, historically known for its steel production.
  • E. Derby
    Derby is a neighborhood within the Brazilian city of Recife, known for its central location and urban character.
  • 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_69a8864526c081908a3a4d74f689e2c5 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa662d13e88190a22b0faf0d848c7d completed March 6, 2026, 5:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69adbf6722f081908c5368a09d1507ac completed March 8, 2026, 6:26 p.m.
Created at: March 4, 2026, 7:32 p.m.