Triple

T1654421
Position Surface form Disambiguated ID Type / Status
Subject Midland Railway E35764 entity
Predicate keyRoute P5619 FINISHED
Object London to Sheffield via Leicester and Derby 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: London to Sheffield via Leicester and Derby | Statement: [Midland Railway, keyRoute, London to Sheffield via Leicester and Derby]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: keyRoute
Context triple: [Midland Railway, keyRoute, London to Sheffield via Leicester and Derby]
  • A. keyRite
    Indicates that an entity performs or is associated with a ritual, ceremony, or formal procedure involving a key (literal or symbolic).
  • B. route chosen
    Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
  • C. key
    Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
  • D. keyTarget
    Indicates that one entity serves as the primary focus, objective, or intended recipient of another entity’s action, function, or influence.
  • E. keySymbol
    Indicates that one entity serves as the symbolic representation or notation used to denote another entity as a key.
  • 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_69a8860568888190a32cd9f70acbba42 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aaf3359ce48190803b322db8ad6027 completed March 6, 2026, 3:31 p.m.
PD Predicate disambiguation batch_69a907cff53c8190b424f088478d3e2c completed March 5, 2026, 4:34 a.m.
Created at: March 4, 2026, 7:29 p.m.