Triple
T28487539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Sway |
E720872
|
entity |
| Predicate | includedInSubscription |
P16605
|
FINISHED |
| Object | Microsoft 365 Personal |
—
|
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: Microsoft 365 Personal | Statement: [Microsoft Sway, includedInSubscription, Microsoft 365 Personal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInSubscription Context triple: [Microsoft Sway, includedInSubscription, Microsoft 365 Personal]
-
A.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
B.
membershipIncluded
Indicates that one entity’s membership or inclusion is contained within, or granted as part of, another entity’s membership.
-
C.
includedSingle
Indicates that one specific, individual item is contained within or made part of another set, group, or collection.
-
D.
includedWith
chosen
Indicates that one entity is provided or packaged together as part of another entity.
-
E.
includedOnSingle
Indicates that something is contained or listed within exactly one specific item, set, or context, and not in any others.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: April 28, 2026, 2:59 a.m.