Triple
T17674719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spec# |
E440617
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | verification-oriented programming language |
C1703
|
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: verification-oriented programming language Context triple: [Spec#, instanceOf, verification-oriented programming language]
-
A.
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.
-
B.
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.
-
C.
strongly typed programming language
A strongly typed programming language is one in which the type of every value is known and enforced at compile time or runtime, preventing operations that are not valid for a given type.
-
D.
statically typed programming language
A statically typed programming language is one in which variable types are checked and fixed at compile time rather than at runtime.
-
E.
programming language
chosen
A programming language is a formal system of syntax and semantics that allows humans to write instructions a computer can execute to perform specific tasks or solve problems.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10 a.m.