Triple
T31770713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VT78 |
E810931
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | DEC computer system |
C44794
|
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: DEC computer system Context triple: [VT78, instanceOf, DEC computer system]
-
A.
DEC operating system
A DEC operating system is a family of Digital Equipment Corporation software platforms (such as VMS and various UNIX variants) designed to manage hardware resources, provide multi-user and multitasking capabilities, and support application execution on DEC minicomputers and workstations.
-
B.
PDP series computer
chosen
A PDP series computer is a family of minicomputers produced by Digital Equipment Corporation (DEC) from the 1960s to 1980s, known for their relatively low cost, interactive use, and significant influence on computer architecture and operating systems.
-
C.
IBM computer
An IBM computer is a computing device or system designed and manufactured by International Business Machines Corporation, historically influential in establishing standards for personal and enterprise computing.
-
D.
S-100 bus computer
An S-100 bus computer is a microcomputer system built around the S-100 expansion bus standard, using a backplane and plug-in cards for CPU, memory, and I/O to create a modular, expandable architecture.
-
E.
mainframe computer
A mainframe computer is a large, powerful, and highly reliable central computer system designed to process vast amounts of data and support numerous simultaneous users and critical applications, typically used by large organizations.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:33 p.m.