Triple

T16469956
Position Surface form Disambiguated ID Type / Status
Subject Coniston branch line E400033 entity
Predicate closedToFreight P37969 FINISHED
Object 1962 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: 1962 | Statement: [Coniston branch line, closedToFreight, 1962]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: closedToFreight
Context triple: [Coniston branch line, closedToFreight, 1962]
  • A. lineClosedToFreight chosen
    Indicates that a railway line is not available for freight services or freight train operations.
  • B. closedFor
    Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
  • C. closedOffFrom
    Indicates that one entity is isolated, blocked, or prevented from accessing, interacting with, or being influenced by another entity.
  • D. closedBy
    Indicates that one entity performs the action of closing, finishing, or terminating another entity (such as a task, issue, or process).
  • E. closedForPassengers
    Indicates that a transportation facility or vehicle is not available for use by passengers.
  • F. None of above.

Provenance (3 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_69d87f2dac988190b74d6e185fa88ba4 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32dcfed6c8190b8dbe4b65b0ab817 completed April 18, 2026, 7:08 a.m.
PD Predicate disambiguation batch_69e227048d608190a4205eae3117629a completed April 17, 2026, 12:26 p.m.
Created at: April 10, 2026, 5:11 a.m.