Triple
T10427084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft BASIC |
E245815
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | BASIC interpreter |
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: BASIC interpreter Context triple: [Microsoft BASIC, instanceOf, BASIC interpreter]
-
A.
BASIC dialect
A BASIC dialect is a specific variant or implementation of the BASIC programming language, typically featuring its own syntax extensions, commands, and runtime behavior tailored to particular platforms or use cases.
-
B.
interpreter
An interpreter is a program or component that directly executes instructions written in a programming or scripting language by reading and performing them line by line without first compiling them into machine code.
-
C.
interpreted programming language
An interpreted programming language is a type of language whose source code is executed directly by an interpreter program, which reads and performs the instructions line by line without requiring prior compilation to machine code.
-
D.
FIRST program
A FIRST program is a structured, mentor-guided robotics and STEM education initiative in which student teams design, build, and program robots to compete in challenge-based events while developing technical and teamwork skills.
-
E.
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.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:12 p.m.