Triple
T32238528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanford Artificial Intelligence Lab self-driving car project (early work) |
E823539
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous vehicle research project |
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 vehicle research project Context triple: [Stanford Artificial Intelligence Lab self-driving car project (early work), instanceOf, autonomous vehicle research project]
-
A.
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.
-
B.
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.
-
C.
autonomous robotic vehicle
An autonomous robotic vehicle is a self-navigating mobile machine that perceives its environment, makes decisions, and moves without direct human control.
-
D.
autonomous navigation system
An autonomous navigation system is a self-directed control framework that enables vehicles or robots to perceive their environment, plan routes, and move safely to a destination without human intervention.
-
E.
autonomous software system
An autonomous software system is a self-governing program that can perceive its environment, make decisions, and act without continuous human intervention to achieve specified goals.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:39 a.m.