Triple
T37932889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft 365 Family |
E946263
|
entity |
| Predicate | includesStoragePerUser |
P85952
|
FINISHED |
| Object | 1000 GB OneDrive cloud storage |
—
|
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: 1000 GB OneDrive cloud storage | Statement: [Microsoft 365 Family, includesStoragePerUser, 1000 GB OneDrive cloud storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesStoragePerUser Context triple: [Microsoft 365 Family, includesStoragePerUser, 1000 GB OneDrive cloud storage]
-
A.
storageDefault
Indicates that something serves as the standard or fallback storage option used when no specific storage choice is provided.
-
B.
storageOption
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
C.
hasStorage
chosen
Indicates that one entity provides or contains storage capacity or space for another entity or resource.
-
D.
storageLimitPolicy
Indicates the rules or constraints that govern how much and how long data or items may be stored.
-
E.
storageProperty
Indicates a relationship where an entity has a specific storage-related characteristic, such as capacity, type, or configuration.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.