Triple
T18653699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scheme: An Interpreter for Extended Lambda Calculus |
E456004
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | programming languages paper |
C5489
|
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: programming languages paper Context triple: [Scheme: An Interpreter for Extended Lambda Calculus, instanceOf, programming languages paper]
-
A.
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.
-
B.
programming language
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.
-
C.
programming language implementation
chosen
A programming language implementation is the concrete realization of a language’s specification, including its compiler or interpreter, runtime system, and associated tools that translate and execute programs written in that language.
-
D.
programming language specification
A programming language specification is a formal document that precisely defines a language’s syntax, semantics, and behavior to ensure consistent implementation and usage across tools and platforms.
-
E.
complexity theory paper
A complexity theory paper is a scholarly work that rigorously analyzes the computational resources required to solve problems, classifies them into complexity classes, and explores relationships or separations between these classes.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.