Triple
T19398121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAE Levels of Driving Automation 0–5 |
E485245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automation classification framework |
C20518
|
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: automation classification framework Context triple: [SAE Levels of Driving Automation 0–5, instanceOf, automation classification framework]
-
A.
classification board
A classification board is an authoritative body or panel that evaluates and assigns categories, ratings, or classifications to items such as media, products, or information based on defined criteria and standards.
-
B.
social classification
Social classification is the systematic process of categorizing individuals or groups within a society based on attributes such as socioeconomic status, ethnicity, gender, occupation, or education, which shapes their access to resources, power, and opportunities.
-
C.
canonical classification
chosen
Canonical classification is a standardized method of organizing entities into universally recognized categories based on their essential, defining characteristics.
-
D.
statistical classification
Statistical classification is the process of assigning items or observations to predefined categories or classes based on their measured features using probabilistic or algorithmic decision rules.
-
E.
artificial intelligence framework
An artificial intelligence framework is a structured software environment that provides tools, libraries, and interfaces to design, train, deploy, and manage AI and machine learning models efficiently.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:36 p.m.