Triple
T28330253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Office LTSC Professional Plus 2021 |
E717518
|
entity |
| Predicate | receivesSecurityUpdates |
P17646
|
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: [Microsoft Office LTSC Professional Plus 2021, receivesSecurityUpdates, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesSecurityUpdates Context triple: [Microsoft Office LTSC Professional Plus 2021, receivesSecurityUpdates, yes]
-
A.
guaranteedSecurityUpdates
chosen
Indicates that one entity commits to providing security-related software updates for another entity for a specified period or under defined conditions.
-
B.
guaranteedOSUpdates
Indicates that one entity commits to providing operating system updates for another entity for a specified period or under certain conditions.
-
C.
softwareUpdate
Indicates that an entity installs, applies, or provides a newer version of software to replace or enhance an existing one.
-
D.
extendedSecurityUpdatesEndDate
Indicates the date on which extended security update support for a product or system ends.
-
E.
softwareUpdatable
Indicates that a software system or component can be modified or upgraded after deployment, typically through patches, updates, or new versions.
- 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_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 12:31 a.m.