Triple

T22648399
Position Surface form Disambiguated ID Type / Status
Subject Chinnor and Princes Risborough Railway E559026 entity
Predicate originalLineClosedCompletely P149054 FINISHED
Object 1980s LITERAL 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: 1980s | Statement: [Chinnor and Princes Risborough Railway, originalLineClosedCompletely, 1980s]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: originalLineClosedCompletely
Context triple: [Chinnor and Princes Risborough Railway, originalLineClosedCompletely, 1980s]
  • A. originalLineOpened
    Indicates that a transportation or service line began its initial operation or was first opened for use.
  • B. mainLineCompleted
    Indicates that the primary or central process, route, or sequence of steps has been fully finished or brought to completion.
  • C. finalLine
    Indicates that something is the last or concluding line in a sequence, text, or structured content.
  • D. fullLine
    Indicates that one entity represents a complete, uninterrupted line rather than a partial or segmented portion.
  • E. closedAsLinearChannel
    Indicates that one entity has been closed or terminated by being converted into or treated as a linear (one-way, sequential) communication channel.
  • 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_69e245489dd88190b1f674acf61c8769 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f17039c2bc8190972a7c169b27005c completed April 29, 2026, 2:43 a.m.
PD Predicate disambiguation batch_69ee6294c4c08190b7e4829f4b9af24b completed April 26, 2026, 7:08 p.m.
PDg Predicate description generation batch_69ee8841e9cc81908d23b34215e3be71 completed April 26, 2026, 9:48 p.m.
Created at: April 17, 2026, 3:05 p.m.