Triple

T31843402
Position Surface form Disambiguated ID Type / Status
Subject Aberystwith and Welsh Coast Railway E812868 entity
Predicate instanceOf P0 FINISHED
Object 19th-century railway company C2005 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: 19th-century railway company
Context triple: [Aberystwith and Welsh Coast Railway, instanceOf, 19th-century railway company]
  • A. British-era railway company
    A British-era railway company is an organization established during the period of British rule to build, operate, and maintain railway lines and related services, typically under colonial economic and administrative policies.
  • B. 19th-century British company
    A 19th-century British company is a business organization established in Britain between 1801 and 1900, typically operating under early industrial capitalism, imperial trade networks, and evolving corporate and legal frameworks of the Victorian era.
  • C. pre-grouping railway company chosen
    A pre-grouping railway company is a privately owned or regionally based railway operator in the United Kingdom that existed before the 1923 Railways Act consolidated most railways into the "Big Four" groups.
  • D. street railway company
    A street railway company is a business entity that owns, operates, and maintains streetcars or trams running on fixed rails along public streets to provide urban passenger transportation.
  • E. joint railway and harbour company
    A joint railway and harbour company is an organization that owns and operates both rail transport infrastructure and port facilities, coordinating the movement of goods and passengers between land and sea.
  • F. None of above.

Provenance (1 batch)

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_69f348eb327881909b4584b925742f6e completed April 30, 2026, 12:19 p.m.
Created at: April 30, 2026, 11:49 p.m.