Triple

T21269425
Position Surface form Disambiguated ID Type / Status
Subject Nottingham–Skegness line E524215 entity
Predicate rollingStockUsed P5426 FINISHED
Object Class 158 NE NERFINISHED

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: Class 158 | Statement: [Nottingham–Skegness line, rollingStockUsed, Class 158]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Class 158
Context triple: [Nottingham–Skegness line, rollingStockUsed, Class 158]
  • A. Class 158 chosen
    Class 158 is a British diesel multiple unit train widely used on regional and intercity services, known for its higher comfort and speed compared to older provincial stock.
  • B. Class 153
    Class 153 is a type of British single-car diesel multiple unit train used primarily for regional and local passenger services.
  • C. Class 150/2
    Class 150/2 is a subclass of the British Rail Class 150 diesel multiple units, built for regional and commuter services on the UK rail network.
  • D. Class 801
    Class 801 is a type of Hitachi-built high-speed electric multiple unit used in the UK as part of the Azuma fleet operated on the East Coast Main Line.
  • E. Class 150/1
    Class 150/1 is a subclass of the British Rail Class 150 diesel multiple units, distinguished by its specific interior layout and configuration for regional passenger services.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b5156d7881909bd4f83676590715 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e73651115081908b5083ba818a6bb1 completed April 21, 2026, 8:33 a.m.
Created at: April 16, 2026, 4:01 p.m.