Triple
T15377250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhattan Project legacy in computing |
E367701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical influence on computing |
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: historical influence on computing Context triple: [Manhattan Project legacy in computing, instanceOf, historical influence on computing]
-
A.
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.
-
B.
historian of technology
A historian of technology studies how technological developments emerge, evolve, and interact with social, cultural, economic, and political contexts over time.
-
C.
stored-program computer
A stored-program computer is a computing system in which both program instructions and data are stored in the same read-write memory, allowing the machine to modify and execute instructions sequentially or conditionally.
-
D.
pioneer in symbolic computation
A pioneer in symbolic computation is an individual or entity that significantly advances the theory, algorithms, or systems enabling computers to manipulate and reason about mathematical symbols and expressions exactly rather than numerically.
-
E.
model of computation
A model of computation is an abstract mathematical framework that defines how algorithms are represented and executed, specifying the rules, operations, and resources available for performing computations.
- F. None of above. chosen
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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:18 a.m.