Triple

T25451748
Position Surface form Disambiguated ID Type / Status
Subject Monsal Head Viaduct E637799 entity
Predicate lineClosedUnder P158533 FINISHED
Object Beeching cuts 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: Beeching cuts | Statement: [Monsal Head Viaduct, lineClosedUnder, Beeching cuts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lineClosedUnder
Context triple: [Monsal Head Viaduct, lineClosedUnder, Beeching cuts]
  • A. notClosedUnder
    Indicates that applying the operation or relation to elements of a set can produce results that do not belong to that set, so the set is not closed under that operation or relation.
  • B. lineClosedToFreight
    Indicates that a railway line is not available for freight services or freight train operations.
  • C. lineBOpened
    Indicates that a specific line B has been opened or activated, transitioning from a closed or inactive state.
  • D. originalLineClosedCompletely
    Indicates that the original line or route has been fully and permanently closed, with no remaining active segments or operations.
  • E. lineSectionOpenedWith
    Indicates that a specific section of a line (such as a route, track, or service line) has been officially opened or put into operation by a particular action or event.
  • F. None of above. chosen

Provenance (4 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_69e75db7c5048190b8da9cd7eeedb610 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f707c8408190b0405250a2c02a03 completed May 2, 2026, 1:07 p.m.
PD Predicate disambiguation batch_69f4683b34748190818428489a226124 completed May 1, 2026, 8:45 a.m.
PDg Predicate description generation batch_69f46d361c348190b5fdfd805ecde01b completed May 1, 2026, 9:07 a.m.
Created at: April 21, 2026, 2:03 p.m.