Triple

T20314704
Position Surface form Disambiguated ID Type / Status
Subject Frankfurt–Paris E510348 entity
Predicate usesRailwayTechnology P129013 FINISHED
Object high-speed rail 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 rail | Statement: [Frankfurt–Paris, usesRailwayTechnology, high-speed rail]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesRailwayTechnology
Context triple: [Frankfurt–Paris, usesRailwayTechnology, high-speed rail]
  • A. usesRailInfrastructureOf
    Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
  • B. hasRailwayTraction chosen
    Indicates that a railway system, line, or vehicle uses a specified type or method of traction (e.g., electric, diesel, steam) for its propulsion.
  • C. isElectricRailway
    Indicates that a given railway system operates using electric power rather than diesel or other forms of propulsion.
  • D. connectsToRailwayNetwork
    Indicates that one entity is physically or functionally linked to a railway network, allowing access or transfer between them.
  • E. railwayUse
    Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
  • 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_69e0b4c7491c8190961113c4283b10b0 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e67786f4dc8190b02a6c2a4338362d completed April 20, 2026, 6:59 p.m.
PD Predicate disambiguation batch_69e55b21b09081909e46691b6f45a07f completed April 19, 2026, 10:45 p.m.
Created at: April 16, 2026, 11:19 a.m.