Triple

T22445460
Position Surface form Disambiguated ID Type / Status
Subject Scheme48 virtual machine E554851 entity
Predicate supportsImplementationTechnique P3047 FINISHED
Object bytecode-based interpretation LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: bytecode-based interpretation | Statement: [Scheme48 virtual machine, supportsImplementationTechnique, bytecode-based interpretation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsImplementationTechnique
Context triple: [Scheme48 virtual machine, supportsImplementationTechnique, bytecode-based interpretation]
  • A. supportsImplementationOf
    Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
  • B. allowedTechnique
    Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
  • C. hasTechnique chosen
    Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
  • D. supportsFeature
    Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
  • E. supportedParadigm
    Indicates that one entity (such as a tool, language, or system) provides functionality or features that enable or are compatible with a particular paradigm or methodological approach.
  • F. None of above.

Provenance (3 batches)

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_69e11e5113208190ab58c6b595f9d1d0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15b46e8ac8190bfa8c611ffcba822 completed April 29, 2026, 1:13 a.m.
PD Predicate disambiguation batch_69e898ad961c819098fd1e46129bddcc completed April 22, 2026, 9:45 a.m.
Created at: April 16, 2026, 8:47 p.m.