Triple

T34800794
Position Surface form Disambiguated ID Type / Status
Subject London–Cardiff E1003212 entity
Predicate hasApproximateFastRailJourneyTimeHours P194919 FINISHED
Object 1.7 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: 1.7 | Statement: [London–Cardiff, hasApproximateFastRailJourneyTimeHours, 1.7]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateFastRailJourneyTimeHours
Context triple: [London–Cardiff, hasApproximateFastRailJourneyTimeHours, 1.7]
  • A. hasApproximateFastRailJourneyTimeMinutes
    Indicates that there is an estimated duration, measured in minutes, for a fast rail journey between two locations.
  • B. railTravelTimeRangeHours
    Indicates the range of time, in hours, that a journey by rail between the related entities is expected to take.
  • C. hasApproximateWalkingTimeTo
    Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
  • D. travelTimeFromTokyoByShinkansen
    Indicates the amount of time required to travel from Tokyo to another location using the Shinkansen (bullet train).
  • E. commuterRailTravelTimeToManhattan
    Indicates the travel time by commuter rail required to reach Manhattan from a given location.
  • 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_69f76db543808190b188c6c86a91491b completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 completed May 8, 2026, 7:18 a.m.
PD Predicate disambiguation batch_69fd8d8a16f08190b9e880901bfa44fe completed May 8, 2026, 7:15 a.m.
PDg Predicate description generation batch_69fd8e5e9ca48190890a2caddc1f9f5c completed May 8, 2026, 7:18 a.m.
Created at: May 3, 2026, 3:59 p.m.