Triple
T36625812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shostak combination method |
E904164
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | method in Satisfiability Modulo Theories |
C64834
|
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: method in Satisfiability Modulo Theories Context triple: [Shostak combination method, instanceOf, method in Satisfiability Modulo Theories]
-
A.
SMT solver competition
An SMT solver competition is an organized event where different Satisfiability Modulo Theories solvers are benchmarked and compared on standardized problem sets to evaluate and advance the state of the art in automated reasoning.
-
B.
framework in automated theorem proving
A framework in automated theorem proving is a structured environment of algorithms, data structures, and interfaces that coordinates the representation of logical formulas, the application of inference rules, and the management of proof search to automatically derive or verify theorems.
-
C.
SAT solver
A SAT solver is a computational tool that determines whether there exists an assignment of truth values to variables that makes a given Boolean formula evaluate to true.
-
D.
SMT-LIB family
The SMT-LIB family is a standardized collection of logical theories, syntactic constructs, and benchmark formats designed to specify and exchange Satisfiability Modulo Theories (SMT) problems across different solvers.
-
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. chosen
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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.