Triple

T14395321
Position Surface form Disambiguated ID Type / Status
Subject MPS E356934 entity
Predicate instanceOf P0 FINISHED
Object language workbench C10734 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: language workbench
Context triple: [MPS, instanceOf, language workbench]
  • A. language server
    A language server is a background process that provides language-specific features—such as code completion, diagnostics, and refactoring—to development tools via a standardized protocol.
  • B. lexical analyzer generator
    A lexical analyzer generator is a tool that automatically produces a lexer (tokenizer) from a formal specification of a programming language’s lexical structure, such as regular expressions and token definitions.
  • C. extension language platform chosen
    An extension language platform is a system that embeds or hosts a scripting or domain-specific language to allow users to customize, automate, and extend the functionality of an application or environment.
  • D. language binding
    A language binding is a software layer that allows code written in one programming language to use libraries or APIs implemented in another language as if they were native.
  • E. linguistic work
    A linguistic work is a created artifact—such as a text, speech, or signed performance—whose primary purpose is to convey meaning through a structured natural or formal language.
  • 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_69d827927c988190ad98bb0360981783 completed April 9, 2026, 10:26 p.m.
Created at: April 10, 2026, 1:16 a.m.