Triple
T5876864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burroughs B5000 ALGOL compiler |
E130647
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-level language compiler |
C5302
|
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: high-level language compiler Context triple: [Burroughs B5000 ALGOL compiler, instanceOf, high-level language compiler]
-
A.
high-level programming language
A high-level programming language is a human-readable language that abstracts away most hardware details, allowing developers to write, understand, and maintain complex programs more easily.
-
B.
compiler
chosen
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.
-
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.
compiled language
A compiled language is a programming language whose source code is translated by a compiler into machine code or an intermediate form before execution, typically resulting in faster runtime performance.
-
E.
programming language implementation
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.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:57 p.m.