Triple
T692599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On Computable Numbers, with an Application to the Entscheidungsproblem |
E13826
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computer science foundational work |
C2654
|
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 science foundational work Context triple: [On Computable Numbers, with an Application to the Entscheidungsproblem, instanceOf, computer science foundational work]
-
A.
computer science book
chosen
A computer science book is a structured, written resource that explains concepts, theories, and practices related to computing, algorithms, programming, and information systems.
-
B.
foundational work in mathematics
Foundational work in mathematics comprises the theories, principles, and formal systems that rigorously define mathematical objects and reasoning, providing a secure logical basis for all mathematical disciplines.
-
C.
computer science school
A computer science school is an educational institution or program dedicated to teaching the principles, theories, and practical skills of computing, programming, and information technology.
-
D.
software foundation
A software foundation is an organization that supports, governs, and promotes the development, maintenance, and open collaboration of software projects and their communities.
-
E.
computer architecture
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.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:36 p.m.