Triple

T16352516
Position Surface form Disambiguated ID Type / Status
Subject Eurotunnel Shuttle E397093 entity
Predicate travelTimeApprox P109944 FINISHED
Object 35 minutes through the tunnel 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: 35 minutes through the tunnel | Statement: [Eurotunnel Shuttle, travelTimeApprox, 35 minutes through the tunnel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: travelTimeApprox
Context triple: [Eurotunnel Shuttle, travelTimeApprox, 35 minutes through the tunnel]
  • A. approximateDrivingTime
    Indicates the estimated amount of time it takes to drive from one location to another under typical conditions.
  • B. approximateTripDuration chosen
    Indicates the estimated length of time required to complete a trip between specified locations or points in a journey.
  • C. travelTimeCategory
    Indicates the qualitative classification of how long a given travel or trip duration is (e.g., short, medium, long).
  • D. hasApproximateWalkingTimeTo
    Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
  • E. travelTimeTypical
    Indicates the usual or expected amount of time it takes to travel between two locations under normal conditions.
  • 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_69d87f26864c819088365ca381a003c2 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2facbf60c8190aa47d4c45ff59354 completed April 18, 2026, 3:30 a.m.
PD Predicate disambiguation batch_69e226f37ecc819082af58b29b4e39d1 completed April 17, 2026, 12:26 p.m.
Created at: April 10, 2026, 5:07 a.m.