Triple
T9566703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindley–Milner type system |
E230805
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | polymorphic type system |
C26025
|
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: polymorphic type system Context triple: [Hindley–Milner type system, instanceOf, polymorphic type system]
-
A.
gradually typed programming language
A gradually typed programming language is one that allows both static and dynamic typing in the same codebase, enabling developers to optionally add or refine type annotations over time.
-
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.
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.
-
D.
uniform system
A uniform system is a conceptual model in which properties such as composition, structure, and behavior are assumed to be consistent and invariant throughout the entire system.
-
E.
identifier resolution system
An identifier resolution system is a mechanism that maps unique identifiers to their corresponding resources or entities, enabling consistent lookup, retrieval, and management across distributed or heterogeneous environments.
- 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:04 p.m.