Triple
T13349687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLOW-MATIC |
E318038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English-like programming language |
C1704
|
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: English-like programming language Context triple: [FLOW-MATIC, instanceOf, English-like programming language]
-
A.
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.
-
B.
high-level programming language
chosen
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:31 p.m.