Triple

T31646538
Position Surface form Disambiguated ID Type / Status
Subject Moscow ML E807597 entity
Predicate instanceOf P0 FINISHED
Object ML-family programming language implementation C5489 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: ML-family programming language implementation
Context triple: [Moscow ML, instanceOf, ML-family programming language implementation]
  • A. 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).
  • B. programming language implementation chosen
    A programming language implementation is the concrete realization of a language’s specification, including its compiler or interpreter, runtime system, and associated tools that translate and execute programs written in that language.
  • C. Haskell infrastructure project
    A Haskell infrastructure project is a foundational software system, tooling, or service built in Haskell that supports, automates, or enhances the development, deployment, and operation of other Haskell applications.
  • D. 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.
  • E. 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.
  • 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_69f348d9ce58819093ea2da83cbeeec1 completed April 30, 2026, 12:19 p.m.
Created at: April 30, 2026, 10:51 p.m.