Triple

T15353698
Position Surface form Disambiguated ID Type / Status
Subject SR 193 E367117 entity
Predicate hasSpeedLimitCharacteristic P118233 FINISHED
Object generally lower speed limits due to curves and residential areas 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: generally lower speed limits due to curves and residential areas | Statement: [SR 193, hasSpeedLimitCharacteristic, generally lower speed limits due to curves and residential areas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSpeedLimitCharacteristic
Context triple: [SR 193, hasSpeedLimitCharacteristic, generally lower speed limits due to curves and residential areas]
  • A. hasSpeedLimit
    Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
  • B. speedLimitCharacteristic
    Indicates that an entity has a specific speed limit property or constraint associated with it.
  • C. hasSpeedLimitRange
    Indicates that there is a specified minimum and maximum speed limit applicable to a given context or segment.
  • D. hasSpeedRestriction
    Indicates that an entity is subject to a specified limit on its allowable speed.
  • E. hasSpeedLimitCategory
    Indicates that an entity is associated with a specific category or classification of speed limit.
  • 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_69d85a1355608190a6673ddb67231d54 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e2a8e88819093e4b7479b2c80cd completed April 16, 2026, 1:40 a.m.
PD Predicate disambiguation batch_69deca991e5081908b0df3d1ee7d5338 completed April 14, 2026, 11:15 p.m.
PDg Predicate description generation batch_69decf2e413481909d9180a8d78d2c17 completed April 14, 2026, 11:35 p.m.
Created at: April 10, 2026, 3:18 a.m.