Triple
T23281134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curry–Howard correspondence |
E588866
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | correspondence between logic and computation |
C28854
|
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: correspondence between logic and computation Context triple: [Curry–Howard correspondence, instanceOf, correspondence between logic and computation]
-
A.
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.
-
B.
logic for concurrent systems
Logic for concurrent systems is a formal framework for specifying and reasoning about the behaviors, interactions, and correctness properties of systems in which multiple processes execute and communicate simultaneously.
-
C.
construction in proof theory
chosen
A construction in proof theory is a systematically defined method or procedure used within formal proofs to build objects, derive new statements, or transform existing proofs while preserving logical validity.
-
D.
nonclassical logic semantics
Nonclassical logic semantics is the study of meaning and truth conditions for logics that deviate from classical principles, such as by altering truth values, inference rules, or structural constraints.
-
E.
interactive theorem prover
An interactive theorem prover is a software system that assists users in the formalization and step-by-step verification of mathematical proofs or program properties through human-guided logical reasoning.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 4:57 p.m.