Triple
T7920695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PDP-11 |
E183936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computer architecture platform |
C4039
|
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: computer architecture platform Context triple: [PDP-11, instanceOf, computer architecture platform]
-
A.
computer architecture
chosen
Computer architecture is the conceptual design and organization of a computer system’s fundamental components and their interactions, defining how hardware and software work together to execute instructions efficiently.
-
B.
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.
-
C.
microprocessor architecture
Microprocessor architecture is the conceptual design and organization of a computer’s central processing unit, defining its instruction set, data paths, control logic, memory hierarchy, and interfaces to efficiently execute programs.
-
D.
GPU architecture
GPU architecture is the conceptual design and organization of a graphics processing unit’s cores, memory hierarchy, and data paths that enable massively parallel computation for graphics and general-purpose workloads.
-
E.
microprocessor
A microprocessor is a compact, integrated circuit that performs the arithmetic, logic, control, and input/output operations of a computer’s central processing unit (CPU) on a single chip.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:06 p.m.