Triple
T7934139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft APIs |
E184248
|
entity |
| Predicate | includes |
P1393
|
FINISHED |
| Object | OneDrive API |
E276968
|
NE 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: OneDrive API | Statement: [Microsoft APIs, includes, OneDrive API]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OneDrive API Context triple: [Microsoft APIs, includes, OneDrive API]
-
A.
OneDrive
OneDrive is Microsoft’s cloud storage and file synchronization service that lets users securely store, access, and share files across devices and online.
-
B.
Zoho WorkDrive
Zoho WorkDrive is a cloud-based file storage, collaboration, and team content management platform offered by Zoho.
-
C.
Microsoft Graph API
chosen
Microsoft Graph API is a unified RESTful endpoint from Microsoft that provides access to a wide range of Microsoft 365 and enterprise mobility services and data through a single programmable interface.
-
D.
Google Drive
Google Drive is a cloud-based file storage and synchronization service by Google that lets users store, share, and access files from any internet-connected device.
-
E.
Naver Drive
Naver Drive is a cloud storage and file-sharing service provided by Naver, allowing users to store, sync, and access files across devices.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aeb132c8190bea4906aaf51b869 |
completed | March 31, 2026, 3:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5c041e588190bfbf251ed88d5bcd |
completed | March 31, 2026, 5:30 a.m. |
Created at: March 30, 2026, 5:08 p.m.