Triple

T29866065
Position Surface form Disambiguated ID Type / Status
Subject Eje Vial system E758459 entity
Predicate typicalSpeedEnvironment P204011 FINISHED
Object urban arterial speeds — 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: urban arterial speeds | Statement: [Eje Vial system, typicalSpeedEnvironment, urban arterial speeds]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalSpeedEnvironment
Context triple: [Eje Vial system, typicalSpeedEnvironment, urban arterial speeds]
  • A. typicalSpeedup
    Indicates the usual or expected performance improvement (e.g., reduction in time or increase in speed) achieved when applying one method, system, or configuration relative to another.
  • B. speedDescribedAs
    Indicates that one entity characterizes or labels the speed of another entity using a particular description or term.
  • C. baseSpeed
    Indicates the default or starting rate at which an entity moves or operates before any modifications or adjustments.
  • D. typicalSpeedLimitComparedToMainline
    Indicates how the typical speed limit on one road segment compares to that of the mainline or primary roadway.
  • E. speedDependsOn
    Indicates that the speed of one entity is determined or influenced by another specified factor or entity.
  • 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_69f2245b4dec8190b85f664d918a00a5 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_6a030c7d03308190a102689db1e8b657 completed May 12, 2026, 11:18 a.m.
PD Predicate disambiguation batch_6a030a57b16c81909191270f64a77fcf completed May 12, 2026, 11:09 a.m.
PDg Predicate description generation batch_6a030c7c58148190bf4bc76e6c5ee8f1 completed May 12, 2026, 11:18 a.m.
Created at: April 29, 2026, 5:51 p.m.