Triple
T26377797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SuperVision |
E660945
|
entity |
| Predicate | automationLevelTarget |
P9537
|
FINISHED |
| Object | SAE Level 3-ready capabilities |
—
|
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: SAE Level 3-ready capabilities | Statement: [SuperVision, automationLevelTarget, SAE Level 3-ready capabilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: automationLevelTarget Context triple: [SuperVision, automationLevelTarget, SAE Level 3-ready capabilities]
-
A.
automationLevel
chosen
Indicates the degree to which a process, task, or system is performed automatically rather than manually.
-
B.
activationLevel
Indicates the degree or intensity to which something is currently active, engaged, or functioning within a given context.
-
C.
targetPerformanceLevel
Indicates the specific performance standard or level that an entity is expected or required to achieve.
-
D.
configurationLevel
Indicates the degree or tier of settings or parameters applied to configure something within a system or context.
-
E.
availabilityTarget
Indicates that something is the intended object, resource, or condition whose availability is being specified, monitored, or constrained.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61071a4c4819090729e0c9789cf21 |
completed | May 2, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 11:02 p.m.