Triple
T32257446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo autonomous driving platform |
E824061
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous driving platform |
C4220
|
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 driving platform Context triple: [Apollo autonomous driving platform, instanceOf, autonomous driving platform]
-
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.
autonomous vehicle project
chosen
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.
-
C.
automotive platform
An automotive platform is a shared, standardized set of structural, mechanical, and electronic components that underpins multiple vehicle models to streamline development, reduce costs, and enable design flexibility.
-
D.
automotive computing platform
An automotive computing platform is an integrated hardware and software system within a vehicle that manages and coordinates functions such as infotainment, driver assistance, connectivity, and vehicle control in a secure and real-time manner.
-
E.
vehicle platform
A vehicle platform is a shared structural and mechanical foundation, including chassis, powertrain, and key components, upon which multiple vehicle models can be built.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:41 a.m.