Triple

T4756241
Position Surface form Disambiguated ID Type / Status
Subject Moscow–Saint Petersburg railway E105594 entity
Predicate servedByTrainType P56947 FINISHED
Object high-speed passenger trains 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: high-speed passenger trains | Statement: [Moscow–Saint Petersburg railway, servedByTrainType, high-speed passenger trains]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servedByTrainType
Context triple: [Moscow–Saint Petersburg railway, servedByTrainType, high-speed passenger trains]
  • A. railwayTypeServed
    Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
  • B. trainTypeUsed chosen
    Indicates that a specific type or category of train is employed or operated in a given context or service.
  • C. railServiceType
    Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
  • D. servedByRailroad
    Indicates that a location or facility is provided with transportation or service by a railroad line or company.
  • E. railSystemType
    Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
  • 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_69bd43f14cac819081c7c69803648211 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64e9d80c819088532921a46ea1d6 completed March 20, 2026, 3:16 p.m.
PD Predicate disambiguation batch_69bd6223defc8190823665a6592c1154 completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:20 p.m.