Triple

T1901926
Position Surface form Disambiguated ID Type / Status
Subject High Speed 1 E37707 entity
Predicate maximumDesignSpeed P2096 FINISHED
Object 300 km/h 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: 300 km/h | Statement: [High Speed 1, maximumDesignSpeed, 300 km/h]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maximumDesignSpeed
Context triple: [High Speed 1, maximumDesignSpeed, 300 km/h]
  • A. maxSpeed chosen
    Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
  • B. hasSpeedLimit
    Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
  • C. speedAchieved
    Indicates that a particular speed has been reached or attained by an entity during an event or action.
  • D. hasSpeedLimitRange
    Indicates that there is a specified minimum and maximum speed limit applicable to a given context or segment.
  • E. maximumTakeoffWeight
    Indicates the greatest allowable weight an aircraft can have at the start of its takeoff roll under specified 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_69a8861be7148190a680937ec451a304 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb34d94fc8190a5bf1e582c77c725 completed March 7, 2026, 5:10 a.m.
PD Predicate disambiguation batch_69abafe9f8b0819086d8f6288511c66d completed March 7, 2026, 4:56 a.m.
Created at: March 4, 2026, 7:35 p.m.