Triple
T4549647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algol 68 Genie |
E110130
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Algol 68 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: Algol 68 implementation Context triple: [Algol 68 Genie, instanceOf, Algol 68 implementation]
-
A.
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.
-
B.
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.
-
C.
compiler system
A compiler system is a software toolchain that translates high-level source code into lower-level machine or intermediate code, performing analysis, optimization, and code generation to produce an executable program.
-
D.
compiler
A compiler is a software tool that translates source code written in a high-level programming language into a lower-level target language, typically machine code or bytecode, while performing analysis and optimizations.
-
E.
ACM program
An ACM program is a software application or system developed, evaluated, or used within the context of the Association for Computing Machinery’s computing, research, and educational activities.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.