Triple
T4978245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAE Level 2 |
E111819
|
entity |
| Predicate | regulatoryClarification |
P60757
|
FINISHED |
| Object | driver is considered in control of the 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: driver is considered in control of the vehicle | Statement: [SAE Level 2, regulatoryClarification, driver is considered in control of the vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryClarification Context triple: [SAE Level 2, regulatoryClarification, driver is considered in control of the vehicle]
-
A.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
B.
regulationAtIssue
Indicates that a specific regulation is the subject of concern, dispute, or analysis in the given context.
-
C.
regulatoryStandard
Indicates that one entity serves as an official rule, guideline, or benchmark that governs, constrains, or evaluates the behavior, quality, or performance of another entity.
-
D.
regulationReason
Indicates the reason or justification for which a regulation is established, applied, or enforced in relation to an entity or activity.
-
E.
regulatoryDocument
Indicates a relationship where one entity serves as a regulatory document that defines rules, standards, or requirements governing another entity.
- 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.