Triple
T23791118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ELPI |
E588092
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | logic programming language implementation |
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: logic programming language implementation Context triple: [ELPI, instanceOf, logic programming language implementation]
-
A.
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.
-
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.
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.
-
D.
Datalog engine
A Datalog engine is a system that evaluates Datalog programs by efficiently computing logical inferences over a set of facts and rules, typically using fixpoint or bottom-up evaluation strategies.
-
E.
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.
- 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:17 p.m.