Triple
T17677415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FDR model checker |
E440674
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | formal verification tool |
C26935
|
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: formal verification tool Context triple: [FDR model checker, instanceOf, formal verification tool]
-
A.
formal verification technique
A formal verification technique is a mathematically rigorous method used to prove or disprove the correctness of a system’s design or implementation with respect to a specified formal specification or property.
-
B.
work on program verification
Work on program verification involves developing and applying formal methods to mathematically prove that software systems satisfy their specified correctness, safety, and security properties.
-
C.
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.
-
D.
proof assistant
A proof assistant is a software tool that helps users construct, check, and manage formal mathematical proofs or program correctness proofs by interacting with a rigorous logical framework.
-
E.
model checking technique
chosen
A model checking technique is a formal verification method that systematically explores all possible states of a system model to automatically determine whether it satisfies specified correctness properties.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:01 a.m.