Triple
T9632823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RPL programming language |
E232847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lisp-like language |
C7088
|
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: Lisp-like language Context triple: [RPL programming language, instanceOf, Lisp-like language]
-
A.
Lisp dialect
chosen
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.
-
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.
Lisp machine
A Lisp machine is a specialized computer system designed to efficiently run the Lisp programming language, featuring hardware and software tightly integrated around Lisp’s execution model.
-
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.
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).
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:11 p.m.