Triple

T28789007
Position Surface form Disambiguated ID Type / Status
Subject Greenbone Security Assistant E726897 entity
Predicate configurationInterfaceFor P91057 FINISHED
Object OpenVAS scan targets 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: OpenVAS scan targets | Statement: [Greenbone Security Assistant, configurationInterfaceFor, OpenVAS scan targets]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: configurationInterfaceFor
Context triple: [Greenbone Security Assistant, configurationInterfaceFor, OpenVAS scan targets]
  • A. exportConfigurationFor
    Indicates that one entity produces and outputs a configuration suitable for use by another specified entity.
  • B. interfaceConfigurationCommand
    Indicates a command that configures or modifies the settings of an interface within a system or device.
  • C. configurationVia chosen
    Indicates that one entity is set up, customized, or controlled through another entity serving as its configuration mechanism or source.
  • D. configurationOptionIn
    Indicates that a specific configuration option belongs to, or is defined within, a particular configuration set, context, or system.
  • E. appliesToConfiguration
    Indicates that something (such as a rule, setting, or operation) is relevant to, affects, or is intended for a particular configuration.
  • 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_69f0319aabec81908368720196f69a35 completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f6c1265c208190aacd2b551f8f0f82 completed May 3, 2026, 3:29 a.m.
PD Predicate disambiguation batch_69f6bd2415fc81908c23c311aebce66f completed May 3, 2026, 3:12 a.m.
Created at: April 28, 2026, 6:22 a.m.