Triple

T14039868
Position Surface form Disambiguated ID Type / Status
Subject Rainhill Trials E337815 entity
Predicate railwayTechnology P3554 FINISHED
Object steam locomotive 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: steam locomotive | Statement: [Rainhill Trials, railwayTechnology, steam locomotive]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railwayTechnology
Context triple: [Rainhill Trials, railwayTechnology, steam locomotive]
  • A. railwayFocus
    Indicates that something is a primary subject, theme, or point of attention specifically in the context of railways or railway-related matters.
  • B. railroadEngineeringFeature chosen
    Indicates a feature, element, or characteristic specifically related to the design, construction, or operation of railroad engineering systems.
  • C. railwayInfrastructureManager
    Indicates that one entity is responsible for managing, maintaining, and operating the railway infrastructure used by another entity.
  • D. railroad
    Indicates that one entity constructs, operates, or provides railroad or train transportation services for another entity or area.
  • E. railcode
    Indicates that an entity is associated with a specific railway code used for identification or classification within a rail system.
  • 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_69d81c664e48819088cbd8f433aeffe5 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de30ee374081908b6b5e8f81dd90f2 completed April 14, 2026, 12:20 p.m.
PD Predicate disambiguation batch_69de05ab36b48190920efb1869bdb1fe completed April 14, 2026, 9:15 a.m.
Created at: April 9, 2026, 10:20 p.m.