Triple
T34101229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Information Processing Language |
E874573
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | list processing 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: list processing language Context triple: [Information Processing Language, instanceOf, list processing language]
-
A.
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.
-
B.
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.
-
C.
Lisp dialect
A Lisp dialect is a specific variant of the Lisp programming language family, defined by its own syntax, semantics, and standard libraries while retaining Lisp’s core features like symbolic expressions and homoiconicity.
-
D.
stack-based language
A stack-based language is a programming language in which operations primarily manipulate a last-in, first-out (LIFO) stack, with most instructions implicitly using the stack for their operands and results.
-
E.
programming language design
Programming language design is the process of defining the syntax, semantics, and features of a language to enable humans to express computations clearly, safely, and efficiently for execution by machines.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:53 a.m.