Triple

T19022306
Position Surface form Disambiguated ID Type / Status
Subject FV104 Samaritan E465515 entity
Predicate maximumSpeedOnRoad P2096 FINISHED
Object about 72 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: about 72 km/h | Statement: [FV104 Samaritan, maximumSpeedOnRoad, about 72 km/h]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maximumSpeedOnRoad
Context triple: [FV104 Samaritan, maximumSpeedOnRoad, about 72 km/h]
  • A. maxSpeed chosen
    Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
  • B. speedLimitCharacteristic
    Indicates that an entity has a specific speed limit property or constraint associated with it.
  • C. hasSpeedLimit
    Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
  • D. typicalSpeedLimitComparedToMainline
    Indicates how the typical speed limit on one road segment compares to that of the mainline or primary roadway.
  • E. hasSpeedRestriction
    Indicates that an entity is subject to a specified limit on its allowable speed.
  • 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_69d8dd025c188190a1d81f5b4ec7e2c6 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6dfa3c88190a057c3385d680cf8 completed April 20, 2026, 7:33 a.m.
PD Predicate disambiguation batch_69e4a2fd80c081908237317a3a883e1c completed April 19, 2026, 9:40 a.m.
Created at: April 10, 2026, 12:02 p.m.