Triple
T31847930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System Configuration |
E812988
|
entity |
| Predicate | ServicesTabFeature |
P60612
|
FINISHED |
| Object | enable or disable Windows services |
—
|
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: enable or disable Windows services | Statement: [System Configuration, ServicesTabFeature, enable or disable Windows services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ServicesTabFeature Context triple: [System Configuration, ServicesTabFeature, enable or disable Windows services]
-
A.
featuresService
chosen
Indicates that one entity provides, includes, or offers a particular service as a notable characteristic or component.
-
B.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
C.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
D.
serviceUnder
Indicates that one entity operates, functions, or is provided under the authority, management, or jurisdiction of another entity.
-
E.
serviceBranchFeature
Indicates that a particular feature, capability, or characteristic is associated with or provided by a specific branch of service.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 30, 2026, 11:50 p.m.