Triple

T11919198
Position Surface form Disambiguated ID Type / Status
Subject Durham railway station E283609 entity
Predicate hasServiceTo P6787 FINISHED
Object Newcastle E402096 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: Newcastle | Statement: [Durham railway station, hasServiceTo, Newcastle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Newcastle
Context triple: [Durham railway station, hasServiceTo, Newcastle]
  • A. Newcastle
    Newcastle is a small suburban village in South Dublin, Ireland, known for its historic character and proximity to Dublin city.
  • B. Newcastle
    Newcastle is a coastal city in New South Wales, Australia, known for its busy port, beaches, and industrial heritage.
  • C. Newcastle
    Newcastle is a settlement within the Parish of St. Andrew, likely a small town or village in a predominantly rural Caribbean island parish.
  • D. Newcastle chosen
    Newcastle is a seaside resort town in County Down, Northern Ireland, known for its beach and as a gateway to the Mourne Mountains.
  • E. Newcastle
    Newcastle is a community in the municipality of Clarington, Ontario, known for its small-town character and location along the north shore of Lake Ontario.
  • 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_69d6ab2c07e88190ba13b0d21fd6cf33 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8e8dff77481908cacf6ad03df34ac completed April 10, 2026, 12:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69f440247cf4819084567f6e1005ef04 completed May 1, 2026, 5:54 a.m.
Created at: April 8, 2026, 9:44 p.m.