Triple
T15889226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Böhm–Jacopini theorem |
E385272
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | result in computer science |
C17349
|
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: result in computer science Context triple: [Böhm–Jacopini theorem, instanceOf, result in computer science]
-
A.
research computer system
A research computer system is a specialized computing environment designed to support complex scientific or academic investigations by providing high-performance processing, large-scale data storage, and advanced analytical tools.
-
B.
computer science problem
chosen
A computer science problem is a well-defined computational task or question that requires designing algorithms, data structures, or formal methods to determine a solution or prove properties about its solvability or complexity.
-
C.
computer science book
A computer science book is a structured, written resource that explains concepts, theories, and practices related to computing, algorithms, programming, and information systems.
-
D.
computer science community
A computer science community is a group of people who share knowledge, collaborate, and support each other around topics in computing, programming, and related technologies.
-
E.
computer science research center
A computer science research center is an institution dedicated to advancing knowledge and innovation in computing through focused research, collaboration, and dissemination of results across areas such as algorithms, systems, artificial intelligence, and human-computer interaction.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:51 a.m.