Triple
T4978185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traffic-Aware Cruise Control |
E111818
|
entity |
| Predicate | canIncreaseSpeedTo |
P3962
|
FINISHED |
| Object | return to set speed when lane ahead is clear |
—
|
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: return to set speed when lane ahead is clear | Statement: [Traffic-Aware Cruise Control, canIncreaseSpeedTo, return to set speed when lane ahead is clear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canIncreaseSpeedTo Context triple: [Traffic-Aware Cruise Control, canIncreaseSpeedTo, return to set speed when lane ahead is clear]
-
A.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
B.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
C.
accelerates
chosen
Indicates that one entity causes an increase in the speed or rate of change of another entity or process.
-
D.
speed
Indicates the rate at which an entity moves or changes position over time.
-
E.
supportsSpeedControls
Indicates that an entity provides or is compatible with mechanisms to adjust or control 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_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. |
Created at: March 20, 2026, 1:33 p.m.