Triple
T18464110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algol family |
E451112
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperative programming language family |
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: imperative programming language family Context triple: [Algol family, instanceOf, imperative programming language family]
-
A.
ALGOL family programming language
An ALGOL family programming language is a high-level, block-structured, imperative language descended from the original ALGOL designs, characterized by clear syntax, lexical scoping, and strong influence on later mainstream languages like Pascal, C, and Java.
-
B.
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.
-
C.
compiled language
A compiled language is a programming language whose source code is translated by a compiler into machine code or an intermediate form before execution, typically resulting in faster runtime performance.
-
D.
functional programming language
A functional programming language is a programming paradigm where computation is treated as the evaluation of mathematical functions, emphasizing immutability, first-class functions, and avoidance of side effects.
-
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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:33 a.m.