Triple

T31337467
Position Surface form Disambiguated ID Type / Status
Subject Harpenden railway station E799214 entity
Predicate hasOperatorAfterPrivatisation P182852 FINISHED
Object Thameslink 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: Thameslink | Statement: [Harpenden railway station, hasOperatorAfterPrivatisation, Thameslink]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOperatorAfterPrivatisation
Context triple: [Harpenden railway station, hasOperatorAfterPrivatisation, Thameslink]
  • A. operatorPrePrivatisation
    Indicates that an entity functioned as the operator of a service or asset before it underwent privatisation.
  • B. ownershipStatusAfterPrivatisation
    Indicates the type or state of ownership an entity has after a privatisation process has taken place.
  • C. acquiredByCurrentOperator
    Indicates that an entity has been obtained or taken over by the operator that currently controls or manages it.
  • D. marketStructureAfterPrivatisation
    Indicates the type or configuration of a market that exists following the process of privatisation of a previously public entity or sector.
  • E. operatedAfter
    Indicates that one operation or action occurred later in time than another specified operation or action.
  • 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_69f224e3f6ac8190a13488516abca7c9 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f794f24e588190965e39b77534d53f completed May 3, 2026, 6:33 p.m.
PD Predicate disambiguation batch_69f791033d288190b118029fe412b9c9 completed May 3, 2026, 6:16 p.m.
PDg Predicate description generation batch_69f791cad5e08190a8a04ca283dbecaa completed May 3, 2026, 6:19 p.m.
Created at: April 29, 2026, 9:16 p.m.