Triple

T16000562
Position Surface form Disambiguated ID Type / Status
Subject Durham Coast Line E388079 entity
Predicate connectsTown P845 FINISHED
Object Billingham E494568 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: Billingham | Statement: [Durham Coast Line, connectsTown, Billingham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Billingham
Context triple: [Durham Coast Line, connectsTown, Billingham]
  • A. Billingham chosen
    Billingham is an industrial town in County Durham, England, known historically for its chemical industry and proximity to the River Tees.
  • B. Leamouth
    Leamouth is a riverside district in East London where the River Lea meets the River Thames, known for its former industrial docks and recent waterside redevelopment.
  • C. Buckhaven
    Buckhaven is a coastal town in eastern Scotland, situated on the Firth of Forth in the historic county of Fife.
  • D. Banham
    Banham is the surname of Reyner Banham, a prominent 20th-century English architectural critic and historian known for his influential writings on modernism and popular culture.
  • E. Jaywick
    Jaywick is a small coastal village in Essex, England, known for its seaside location and history of deprivation and flood risk.
  • 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_69d86daa562c81908aacc179c0fe8fb5 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e157fba9748190ac8fc27b167d49f7 completed April 16, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffc3d99ca08190a3d07a0802b1b24a completed May 9, 2026, 11:31 p.m.
Created at: April 10, 2026, 4:55 a.m.