human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "depending on session typed processes"
  Abstract: This work proposes a dependent type theory that combines functions and session-typed processes (with value dependencies) through a contextual monad, internalising typed processes in a dependently-typed lambda-calculus. The proposed framework, by allowing session processes to depend on functions and vice-versa, enables us to specify and statically verify protocols where the choice of the next communication action can depend on specific values of received data. Moreover, the type theoretic nature of the framework endows us with the ability to internally describe and prove predicates on process behaviours. Our main results are type soundness of the framework, and a faithful embedding of the functional layer of the calculus within the session-typed layer, showcasing the expressiveness of dependent session types.

Connected through hyperedge HE-1 (induced by source paper "label dependent session types"):
  with members:
    - "dependent session types"
    - "recalling a witness foundations and applications of monotonic state"
    - "linear haskell practical linearity in a higher order polymorphic language"
    - "set theoretic types for polymorphic variants"
    - "sessions as propositions"
    - "complete and easy bidirectional typechecking for higher rank polymorphism"
    - "irrelevance heterogeneous equality and call by value dependent type systems"
    - "linear dependent types and relative completeness"

Connected through hyperedge HE-2 (induced by source paper "intrinsically typed mechanized semantics for session types"):
  with members:
    - "using session types as an effect system"
    - "general recursion via coinductive types"

Connected through hyperedge HE-3 (induced by source paper "value dependent session design in a dependently typed language"):
  with members:
    - "a type and scope safe universe of syntaxes with binding their semantics and proofs"
    - "types from data making structured data first class citizens in f"

Connected through hyperedge HE-4 (induced by source paper "gradual session types"):
  with members:
    - "gradual parametricity revisited"
    - "gradual liquid type inference"
    - "fast and precise type checking for javascript"
    - "sums of uncertainty refinements go gradual"
    - "design and implementation of concurrent c0"
    - "do be do be do"
    - "an erlang implementation of multiparty session actors"
    - "programming with algebraic effects and handlers"

Question: Please tell me which class the center node belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.PL(Programming Languages)