Triple
T24974668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Reactive Engine |
E624984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early computing paper |
C35986
|
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: early computing paper Context triple: [The Reactive Engine, instanceOf, early computing paper]
-
A.
early computer
An early computer is a large, often room-sized electronic or electromechanical machine designed in the mid-20th century to perform basic calculations and data processing using primitive hardware and limited programming capabilities.
-
B.
historical influence on computing
chosen
Historical influence on computing encompasses the people, events, technologies, and social forces from the past that have shaped the development, adoption, and evolution of computer systems and concepts over time.
-
C.
historical computer architecture
Historical computer architecture is the study and classification of past computer system designs, components, and organizational principles that shaped the evolution of computing hardware over time.
-
D.
ARPANET-era document
An ARPANET-era document is a digital or scanned artifact originating from the early internet’s ARPANET period, typically containing technical, administrative, or research information that reflects the network’s foundational development and usage.
-
E.
first-generation computer
A first-generation computer is an early electronic computing device (circa 1940s–1950s) that used vacuum tubes, magnetic drums, and machine or assembly language to perform basic calculations and data processing.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:01 a.m.