Triple
T4978184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traffic-Aware Cruise Control |
E111818
|
entity |
| Predicate | canReduceSpeedTo |
P60754
|
FINISHED |
| Object | match speed of leading vehicle |
—
|
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: match speed of leading vehicle | Statement: [Traffic-Aware Cruise Control, canReduceSpeedTo, match speed of leading vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canReduceSpeedTo Context triple: [Traffic-Aware Cruise Control, canReduceSpeedTo, match speed of leading vehicle]
-
A.
isSlowingDown
Indicates that an entity’s speed or rate of activity is decreasing over time.
-
B.
regulatesSpeedLimitBy
Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
-
C.
hasVariableSpeedLimits
Indicates that the subject is associated with speed limits that can change depending on conditions, time, or location.
-
D.
slowerThan
Indicates that one entity moves or operates at a lower speed than another entity.
-
E.
hasSpeedRestriction
Indicates that an entity is subject to a specified limit on its allowable speed.
- 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_69bd441adc208190b70a033a0741d01e |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:33 p.m.