Triple
T33671769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALGOL Y |
E862635
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ALGOL variant |
C2955
|
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 variant Context triple: [ALGOL Y, instanceOf, ALGOL variant]
-
A.
ALGOL family programming language
chosen
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.
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.
-
C.
CP/M variant
A CP/M variant is an operating system derived from or compatible with the original CP/M, typically adapted to specific hardware platforms or extended with additional features while retaining CP/M-like functionality.
-
D.
fourth-generation programming environment
A fourth-generation programming environment is a high-level software development platform that enables users to create applications using declarative, domain-specific tools and minimal traditional coding, often through visual interfaces and automated code generation.
-
E.
Algic language
An Algic language is any member of a family of Indigenous languages of North America, including the Algonquian branch and a few related languages, that share common ancestral linguistic features.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:43 a.m.