Triple

T6115438
Position Surface form Disambiguated ID Type / Status
Subject Burry Port E136348 entity
Predicate servedBy P82 FINISHED
Object Burry Port railway station E442371 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: Burry Port railway station | Statement: [Burry Port, servedBy, Burry Port railway station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Burry Port railway station
Context triple: [Burry Port, servedBy, Burry Port railway station]
  • A. Burry Port railway station chosen
    Burry Port railway station is a coastal railway station in Carmarthenshire, Wales, serving the town of Burry Port on the West Wales Line.
  • B. Porth railway station
    Porth railway station is a local train station in Porth, Rhondda Cynon Taf, Wales, providing passenger rail services on the Rhondda Line.
  • C. Longport railway station
    Longport railway station is a railway station serving the Longport area of Stoke-on-Trent in Staffordshire, England.
  • D. Maryport railway station
    Maryport railway station is a small coastal rail stop in Cumbria, England, serving the town of Maryport with regional passenger services.
  • E. Heysham Port railway station
    Heysham Port railway station is a small terminus in Lancashire, England, serving passengers traveling to and from the nearby Heysham ferry port.
  • 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_69c0089ea6f88190b349be53e04b4f5f completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c05bc246e48190b4f3d52eb682aa45 completed March 22, 2026, 9:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1256aa9f8819090fdc98343af6f8e completed March 23, 2026, 11:35 a.m.
Created at: March 22, 2026, 4:14 p.m.