Triple

T38451800
Position Surface form Disambiguated ID Type / Status
Subject MVE E912192 entity
Predicate usedInOperationalSystems P16239 FINISHED
Object yes 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: yes | Statement: [MVE, usedInOperationalSystems, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedInOperationalSystems
Context triple: [MVE, usedInOperationalSystems, yes]
  • A. usedByOperatingSystems chosen
    Indicates that something (such as a component, standard, or feature) is utilized or supported by one or more operating systems.
  • B. systemUsedBy
    Indicates that a particular system is utilized or operated by a specified agent or user.
  • C. operatesSystem
    Indicates that an entity actively controls, manages, or runs a particular system.
  • D. relatedOperatingSystem
    Indicates that there is an association between an entity and an operating system that is relevant to its use, compatibility, or operation.
  • E. operatingSystemWorkedOn
    Indicates that an entity has worked on developing, maintaining, or contributing to a particular operating system.
  • 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_69f76e84e2dc81908badf05b3aafa9ea completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69ff46afe7e481908f2862ed11c88db2 completed May 9, 2026, 2:37 p.m.
PD Predicate disambiguation batch_69ff45e9151881909c444a655e852165 completed May 9, 2026, 2:34 p.m.
Created at: May 3, 2026, 4:31 p.m.