Triple
T36789682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC3 model checking algorithm |
E909016
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | safety property verification technique |
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: safety property verification technique Context triple: [IC3 model checking algorithm, instanceOf, safety property verification technique]
-
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.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.