Triple

T3119582
Position Surface form Disambiguated ID Type / Status
Subject XRF E65148 entity
Predicate appliesToTransportMode P45471 FINISHED
Object 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: rail | Statement: [XRF, appliesToTransportMode, rail]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliesToTransportMode
Context triple: [XRF, appliesToTransportMode, rail]
  • A. appliesToTransitSystem
    Indicates that something (such as a rule, policy, feature, or condition) is relevant or applicable to a particular transit or transportation system.
  • B. appliedToVehicleType
    Indicates that something (such as a rule, restriction, or condition) is specifically applicable to a particular type or category of vehicle.
  • C. appliesToTransitLine
    Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular transit line.
  • D. isPublicTransport
    Indicates that the entity functions as a mode or instance of transportation that is available for use by the general public, typically operating on fixed routes or schedules.
  • E. transportModeAccess
    Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
  • 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_69ad857fcc088190b0c4d45a5cde6f61 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada4eb6a6081909df41f67999eb4ff completed March 8, 2026, 4:33 p.m.
PD Predicate disambiguation batch_69ad9df455088190940ad04419772dc8 completed March 8, 2026, 4:04 p.m.
PDg Predicate description generation batch_69ada0f7c21c819087e9992f5fe30a37 completed March 8, 2026, 4:16 p.m.
Created at: March 8, 2026, 3:04 p.m.