Triple

T5707764
Position Surface form Disambiguated ID Type / Status
Subject InterCity CrossCountry E125826 entity
Predicate railwayOperatorRole P20222 FINISHED
Object provided through services between regions 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: provided through services between regions | Statement: [InterCity CrossCountry, railwayOperatorRole, provided through services between regions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railwayOperatorRole
Context triple: [InterCity CrossCountry, railwayOperatorRole, provided through services between regions]
  • A. railNetworkRole
    Indicates the specific function or responsibility an entity has within a rail network system.
  • B. trainOperator chosen
    Indicates that one entity operates, manages, or runs train services for another entity or within a specific rail system.
  • C. railwayLineRole
    Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
  • D. hasRailOperatorNamedAfter
    Indicates that a rail operator is named after the specified entity.
  • E. hasLocalRailOperator
    Indicates that a specified rail operator is responsible for providing local or regional rail services within a particular area or network.
  • 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_69c0082d6fe48190b777fb383769e5c8 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c024892fd88190a91133fc88365410 completed March 22, 2026, 5:19 p.m.
PD Predicate disambiguation batch_69c021c2d8bc8190b947c7d1f423d2f3 completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:45 p.m.