Triple
T28330257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Office LTSC Professional Plus 2021 |
E717518
|
entity |
| Predicate | supportsActivationMethod |
P58199
|
FINISHED |
| Object | Key Management Service |
—
|
NE NERFINISHED |
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: Key Management Service | Statement: [Microsoft Office LTSC Professional Plus 2021, supportsActivationMethod, Key Management Service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsActivationMethod Context triple: [Microsoft Office LTSC Professional Plus 2021, supportsActivationMethod, Key Management Service]
-
A.
supportsSignInMethod
Indicates that one entity enables or allows another entity to use a particular sign-in or authentication method.
-
B.
supportsProvisioningMethod
Indicates that one entity is capable of using or is compatible with a particular provisioning method offered or required by another entity.
-
C.
canBeActivatedFor
Indicates that one entity is capable of being put into an active or operational state by or for another entity.
-
D.
activationType
chosen
Indicates the specific manner or mechanism by which an activation or triggering event occurs between entities.
-
E.
supportsAllocationMethods
Indicates that one entity enables, is compatible with, or provides mechanisms for using specific allocation methods associated with another entity.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a008ac37dc081908d360574912f40ec |
completed | May 10, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_6a008a67d73881909855ab4cfca3c399 |
completed | May 10, 2026, 1:38 p.m. |
Created at: April 28, 2026, 12:31 a.m.