Triple

T24288687
Position Surface form Disambiguated ID Type / Status
Subject Eastern Union Railway E605748 entity
Predicate railwaySystemPartOf P155710 FINISHED
Object British railway network 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: British railway network | Statement: [Eastern Union Railway, railwaySystemPartOf, British railway network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railwaySystemPartOf
Context triple: [Eastern Union Railway, railwaySystemPartOf, British railway network]
  • A. railwaySystemServed
    Indicates that a railway system provides service to, or operates within, a specified location or area.
  • B. railSystemType
    Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
  • C. hasRailSystem
    Indicates that an entity possesses or is served by a rail-based transportation system.
  • D. isNationalRailwaySystemOf
    Indicates that one entity functions as the official national railway system serving and operating within the territory of another entity.
  • E. usesRailInfrastructureOf
    Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
  • 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_69e295480d0c8190846fc3c2e2da1d4c completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f28f5908e08190a9f150df924a7160 completed April 29, 2026, 11:08 p.m.
PD Predicate disambiguation batch_69f1c457a2908190993824395b3c365d completed April 29, 2026, 8:41 a.m.
PDg Predicate description generation batch_69f27a753ca8819095706970d368f762 completed April 29, 2026, 9:39 p.m.
Created at: April 18, 2026, 12:08 a.m.