Triple
T29737564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft 365 A3 |
E752504
|
entity |
| Predicate | licenseChannel |
P104066
|
FINISHED |
| Object | volume licensing |
—
|
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: volume licensing | Statement: [Microsoft 365 A3, licenseChannel, volume licensing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseChannel Context triple: [Microsoft 365 A3, licenseChannel, volume licensing]
-
A.
licensingChannel
chosen
Indicates the medium or route through which a license is obtained, distributed, or managed between parties.
-
B.
licenseFor
Indicates that one entity grants or holds formal permission or authorization for another entity to perform an activity, use a resource, or operate under specified conditions.
-
C.
licensePublisher
Indicates that an entity is the organization or agent responsible for issuing or publishing a particular license.
-
D.
licenseBlock
Indicates that an entity is prohibited or restricted from using a license or licensed resource.
-
E.
licenseModel
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 7:46 p.m.