Triple
T4554961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hack |
E120458
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gradually typed programming language |
C17177
|
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: gradually typed programming language Context triple: [Hack, instanceOf, gradually typed programming language]
-
A.
statically typed programming language
A statically typed programming language is one in which variable types are checked and fixed at compile time rather than at runtime.
-
B.
strongly typed programming language
A strongly typed programming language is one in which the type of every value is known and enforced at compile time or runtime, preventing operations that are not valid for a given type.
-
C.
functional programming language
A functional programming language is a programming paradigm where computation is treated as the evaluation of mathematical functions, emphasizing immutability, first-class functions, and avoidance of side effects.
-
D.
compiled language
A compiled language is a programming language whose source code is translated by a compiler into machine code or an intermediate form before execution, typically resulting in faster runtime performance.
-
E.
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.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
Created at: March 20, 2026, 1:09 p.m.