Triple
T29986720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BeanShell |
E761752
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Java-like scripting language |
C1703
|
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: Java-like scripting language Context triple: [BeanShell, instanceOf, Java-like scripting language]
-
A.
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.
-
B.
prototype-based programming language
A prototype-based programming language is a style of object-oriented language where objects are created by cloning existing prototype objects rather than instantiating classes, and behavior is shared via delegation to these prototypes.
-
C.
ML-family language
An ML-family language is a statically typed, functional-first programming language lineage characterized by type inference, algebraic data types, pattern matching, and a strong, expressive type system originating from the MetaLanguage (ML).
-
D.
programming language
chosen
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.
-
E.
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.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:36 p.m.