Triple

T11655447
Position Surface form Disambiguated ID Type / Status
Subject SQL Server Agent E277001 entity
Predicate isDisabledByDefaultIn P11582 FINISHED
Object some SQL Server Express editions 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: some SQL Server Express editions | Statement: [SQL Server Agent, isDisabledByDefaultIn, some SQL Server Express editions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isDisabledByDefaultIn
Context triple: [SQL Server Agent, isDisabledByDefaultIn, some SQL Server Express editions]
  • A. disabledByDefaultIn chosen
    Indicates that a feature, capability, or setting is turned off by default within the specified context or environment.
  • B. canBeDisabledOn
    Indicates that a feature, function, or capability has the property that it can be turned off or deactivated when applied to the referenced entity.
  • C. isDefaultFor
    Indicates that something serves as the standard or fallback option that is automatically applied or selected for a given entity or context unless another choice is explicitly specified.
  • D. enabledBy
    Indicates that one entity functions as the cause, condition, or resource that makes it possible for another entity’s action, state, or capability to occur or be realized.
  • E. appliesByDefaultWhen
    Indicates that one condition, rule, or behavior is automatically in effect whenever a specified situation or context occurs, without requiring explicit activation.
  • 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_69d6aafbb3c081908a9cdb4ecb8d981d completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a3cee010819089cffdbefe5a6efb completed April 10, 2026, 7:16 a.m.
PD Predicate disambiguation batch_69d85ddc780481909a3bc63832fe2bd2 completed April 10, 2026, 2:18 a.m.
Created at: April 8, 2026, 9:39 p.m.