Triple

T8689807
Position Surface form Disambiguated ID Type / Status
Subject London–Brussels E206256 entity
Predicate becameFullyHighSpeedEndToEnd P84206 FINISHED
Object 2007 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: 2007 | Statement: [London–Brussels, becameFullyHighSpeedEndToEnd, 2007]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: becameFullyHighSpeedEndToEnd
Context triple: [London–Brussels, becameFullyHighSpeedEndToEnd, 2007]
  • A. isEndToEnd
    Indicates that a process, system, or connection spans the entire sequence from initial input or start point through to the final output or end point without interruption or intermediate breaks.
  • B. completedAsFreeway
    Indicates that a roadway segment has been fully constructed or upgraded to meet freeway standards, typically implying controlled access and grade-separated intersections.
  • C. hasEnd
    Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
  • D. endTimeAsCCPBase
    Indicates the point in time at which an event or process concludes, expressed using the CCP base time representation.
  • E. endTimeAsCapital
    Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
  • 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_69ca835481fc819084e33d3bc883bfa6 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5734602c81909a0687e00f4a4a26 completed March 31, 2026, 11:22 p.m.
PD Predicate disambiguation batch_69cc4569f9048190b9c86b4c81103d35 completed March 31, 2026, 10:06 p.m.
PDg Predicate description generation batch_69cc483f06f48190879f4702c8b4ed00 completed March 31, 2026, 10:18 p.m.
Created at: March 30, 2026, 6:33 p.m.