Triple
T9187738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AmigaBASIC |
E220500
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | BASIC dialect |
C25786
|
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 dialect Context triple: [AmigaBASIC, instanceOf, BASIC dialect]
-
A.
Lisp dialect
A Lisp dialect is a specific variant of the Lisp programming language family, defined by its own syntax, semantics, and standard libraries while retaining Lisp’s core features like symbolic expressions and homoiconicity.
-
B.
JavaScript dialect
A JavaScript dialect is a language variant that extends or modifies standard JavaScript syntax and semantics while typically compiling or transpiling down to regular JavaScript for execution.
-
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.
Burroughs software system
A Burroughs software system is an integrated suite of programs and operating environments designed for Burroughs mainframe computers, emphasizing stack-based architecture, high-level language support, and robust transaction processing.
-
E.
Batanic language
The Batanic language is a subgroup of Austronesian languages spoken primarily in the Batanes Islands of the northern Philippines and nearby areas, characterized by shared phonological and lexical features distinct from neighboring Philippine languages.
- F. None of above. chosen
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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:24 p.m.