Triple
T32258423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRISM probabilistic model checker |
E824082
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | probabilistic model checker |
C26934
|
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: probabilistic model checker Context triple: [PRISM probabilistic model checker, instanceOf, probabilistic model checker]
-
A.
model checking technique
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.
-
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.
probabilist
A probabilist is a mathematician or scientist who studies probability theory, focusing on the analysis and modeling of random phenomena and uncertainty.
-
D.
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.
-
E.
formal verification technique
chosen
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.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:41 a.m.