Triple
T22446328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ML language family |
E554871
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | functional programming language family |
C7022
|
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: functional programming language family Context triple: [ML language family, instanceOf, functional programming language family]
-
A.
functional programming language
chosen
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.
-
B.
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.
-
C.
ML-family language
An ML-family language is a statically typed, functional-first programming language lineage characterized by type inference, algebraic data types, pattern matching, and a strong, expressive type system originating from the MetaLanguage (ML).
-
D.
dependently typed programming language
A dependently typed programming language is one in which types can depend on values, enabling the expression and static verification of rich logical properties directly in the type system.
-
E.
gradually typed programming language
A gradually typed programming language is one that allows both static and dynamic typing in the same codebase, enabling developers to optionally add or refine type annotations over time.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:47 p.m.