Triple
T36521547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decision Problems in the Theory of Automata |
E900194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computer science work |
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: computer science work Context triple: [Decision Problems in the Theory of Automata, instanceOf, computer science work]
-
A.
computer science academic
A computer science academic is a scholar who conducts research, teaches, and advances knowledge in areas such as algorithms, systems, theory, and applications of computing.
-
B.
computer science repository
A computer science repository is a structured digital storage space that organizes, manages, and provides access to code, documentation, datasets, and related resources for software development and research in computer science.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.