Triple
T5923228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revised^n Report on the Algorithmic Language Scheme |
E131744
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | standard for Scheme programming language |
C7085
|
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: standard for Scheme programming language Context triple: [Revised^n Report on the Algorithmic Language Scheme, instanceOf, standard for Scheme programming language]
-
A.
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.
-
B.
programming language specification
chosen
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.
-
C.
software standard
A software standard is an agreed-upon set of rules, formats, and practices that ensures compatibility, interoperability, and quality across different software systems and components.
-
D.
ECMA standard
An ECMA standard is a formal specification published by Ecma International that defines interoperable technologies, such as programming languages and data formats, to ensure consistency and compatibility across implementations.
-
E.
IEEE standard
An IEEE standard is a formally documented set of technical specifications and guidelines developed and maintained by the Institute of Electrical and Electronics Engineers to ensure interoperability, safety, and quality across electrical, electronic, and computing technologies.
- 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4 p.m.