Triple
T13625073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurora Innovation |
E325557
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous vehicle technology company |
C7714
|
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: autonomous vehicle technology company Context triple: [Aurora Innovation, instanceOf, autonomous vehicle technology company]
-
A.
autonomous driving technology
Autonomous driving technology encompasses the hardware, software, and algorithms that enable vehicles to perceive their environment, make driving decisions, and control motion with minimal or no human intervention.
-
B.
automotive software company
chosen
A company that designs, develops, and maintains software solutions specifically for vehicles and the automotive industry, such as embedded systems, driver assistance, connectivity, and fleet management platforms.
-
C.
autonomous vehicle project
An autonomous vehicle project is an organized effort to design, develop, test, and deploy self-driving systems that enable vehicles to perceive their environment, make driving decisions, and operate safely with minimal or no human intervention.
-
D.
car manufacturer
A car manufacturer is a company that designs, engineers, and assembles automobiles and related components for sale under one or more brand names.
-
E.
transportation services company
A transportation services company is an organization that plans, manages, and operates the movement of people or goods using various modes of transport, such as road, rail, air, or sea, often providing logistics, scheduling, and support services.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:50 p.m.