Triple
T20836539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAT problem |
E512973
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Boolean satisfiability problem |
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: Boolean satisfiability problem Context triple: [SAT problem, instanceOf, Boolean satisfiability problem]
-
A.
collection of decision problems in group theory
A collection of decision problems in group theory is a conceptual class comprising questions that ask, for various groups and inputs, whether certain algebraic properties or relations hold, such as the word, conjugacy, or isomorphism problems.
-
B.
Synoptic problem solution
A synoptic problem solution is a scholarly theory that explains the literary relationships and shared material among the Synoptic Gospels—Matthew, Mark, and Luke—by proposing specific sources, dependencies, or compositional models.
-
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.
automated theorem proving technique
An automated theorem proving technique is a systematic, algorithmic method used by computer programs to derive logical conclusions and verify the validity of mathematical or logical statements without human intervention.
-
E.
theorem prover
A theorem prover is a software system or algorithm that automatically or semi-automatically checks the validity of logical statements by deriving conclusions from axioms and inference rules.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:42 p.m.