Triple

T8720313
Position Surface form Disambiguated ID Type / Status
Subject MP 05 E206992 entity
Predicate railwaySignallingCompatibility P40340 FINISHED
Object automatic train control 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: automatic train control | Statement: [MP 05, railwaySignallingCompatibility, automatic train control]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railwaySignallingCompatibility
Context triple: [MP 05, railwaySignallingCompatibility, automatic train control]
  • A. usesRailwaySignallingSystem chosen
    Indicates that one entity operates or applies a particular railway signalling system in the context of train or rail traffic control.
  • B. railcode
    Indicates that an entity is associated with a specific railway code used for identification or classification within a rail system.
  • C. railwaySign
    Indicates that one entity functions as a railway-related sign or signal that conveys information or instructions within a rail transport context to another entity.
  • D. railwaySignificance
    Indicates the importance or role that a railway or rail-related feature has within a transportation network, region, or context.
  • E. railInterface
    Indicates a connection or interaction between entities via a rail-based system or interface.
  • 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_69ca835811d8819081ea00fd2a2c9a1c completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5d02a52c81909f93622ae6920b80 completed March 31, 2026, 11:47 p.m.
PD Predicate disambiguation batch_69cc457093188190959287a6458651c6 completed March 31, 2026, 10:06 p.m.
Created at: March 30, 2026, 6:36 p.m.