Triple
T18750307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 26262 |
E458508
|
entity |
| Predicate | introduces |
P201
|
FINISHED |
| Object | Automotive Safety Integrity Level |
—
|
NE NERFINISHED |
How this triple was built (3 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: Automotive Safety Integrity Level | Statement: [ISO 26262, introduces, Automotive Safety Integrity Level]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Automotive Safety Integrity Level Context triple: [ISO 26262, introduces, Automotive Safety Integrity Level]
-
A.
ISO 26262
ISO 26262 is an international functional safety standard for electrical and electronic systems in production automobiles, defining requirements to ensure the safety of road vehicles throughout their lifecycle.
-
B.
ISO 21448
ISO 21448 is an international standard that defines safety requirements and guidance for the functional safety and performance limitations of advanced driver assistance systems and automated driving features, often referred to as the Safety of the Intended Functionality (SOTIF).
-
C.
SAE Levels of Driving Automation 0–5
SAE Levels of Driving Automation 0–5 is a standardized classification framework defined by SAE International that categorizes vehicle automation from no automation to full self-driving capability.
-
D.
ISO/IEC 16262
ISO/IEC 16262 is the international standard that formally defines the ECMAScript programming language, the basis for JavaScript and related implementations.
-
E.
ISO 15740
ISO 15740 is the international standard that defines the Picture Transfer Protocol (PTP) used for transferring images and related data between digital cameras and other devices.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Automotive Safety Integrity Level Target entity description: Automotive Safety Integrity Level (ASIL) is a risk classification scheme used in automotive functional safety to define the necessary safety requirements and rigor for electronic and electrical systems based on the severity, exposure, and controllability of potential hazards.
-
A.
ISO 26262
chosen
ISO 26262 is an international functional safety standard for electrical and electronic systems in production automobiles, defining requirements to ensure the safety of road vehicles throughout their lifecycle.
-
B.
ISO 21448
ISO 21448 is an international standard that defines safety requirements and guidance for the functional safety and performance limitations of advanced driver assistance systems and automated driving features, often referred to as the Safety of the Intended Functionality (SOTIF).
-
C.
SAE Levels of Driving Automation 0–5
SAE Levels of Driving Automation 0–5 is a standardized classification framework defined by SAE International that categorizes vehicle automation from no automation to full self-driving capability.
-
D.
ISO/IEC 16262
ISO/IEC 16262 is the international standard that formally defines the ECMAScript programming language, the basis for JavaScript and related implementations.
-
E.
ISO 15740
ISO 15740 is the international standard that defines the Picture Transfer Protocol (PTP) used for transferring images and related data between digital cameras and other devices.
- F. None of above.
Provenance (2 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579ec71cc8190bb6d3fa6cca6dc8c |
completed | April 20, 2026, 12:57 a.m. |
Created at: April 10, 2026, 11:51 a.m.