Triple
T11330595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Safety Sense |
E268332
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive safety technology suite |
C17476
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: automotive safety technology suite Context triple: [Toyota Safety Sense, instanceOf, automotive safety technology suite]
-
A.
automotive safety system
chosen
An automotive safety system is an integrated set of components and technologies designed to prevent accidents or reduce injury and damage when collisions occur.
-
B.
advanced driver-assistance system
An advanced driver-assistance system is an integrated set of vehicle technologies that monitor the driving environment and vehicle status to assist the driver in controlling the car, enhancing safety, comfort, and efficiency.
-
C.
public safety system
A public safety system is an integrated framework of technologies, policies, and coordinated services designed to prevent, detect, respond to, and recover from threats or emergencies affecting the well-being of a community.
-
D.
whiplash protection system
A whiplash protection system is a vehicle safety feature designed to reduce neck and spine injuries during rear-end collisions by controlling seat and headrest movement to support the occupant’s head and torso.
-
E.
automotive all-wheel-drive system
An automotive all-wheel-drive system is a drivetrain configuration that automatically distributes engine power to all four wheels to enhance traction, stability, and handling across varying road and weather conditions.
- F. None of above.
Provenance (1 batch)
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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:32 p.m.