Triple
T14793116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Design by Contract |
E347705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | formal specification approach |
C23037
|
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 specification approach Context triple: [Design by Contract, instanceOf, formal specification approach]
-
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.
formal language specification
A formal language specification is a precise, mathematically defined description of the syntax and structure of a language, typically using grammars and formal rules to unambiguously determine which strings belong to the language.
-
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.
axiomatic semantics
Axiomatic semantics is a formal method for defining the meaning of programs by specifying logical assertions (preconditions and postconditions) that describe the behavior and correctness of program constructs.
-
E.
specification
chosen
A specification is a detailed, precise description of requirements, behaviors, and constraints that a system, component, or process must satisfy.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:31 a.m.