Triple
T8920148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power BI workspaces |
E212392
|
entity |
| Predicate | hasLicenseMode |
P50497
|
FINISHED |
| Object | Pro workspace |
—
|
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: Pro workspace | Statement: [Power BI workspaces, hasLicenseMode, Pro workspace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLicenseMode Context triple: [Power BI workspaces, hasLicenseMode, Pro workspace]
-
A.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
-
B.
hasLicense
Indicates that an entity possesses a valid authorization or permit, typically granted by an authority, to perform a specific activity or use something.
-
C.
usesLicensingModel
chosen
Indicates that one entity employs or applies a particular licensing model in its operations or offerings.
-
D.
supportsLicense
Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
-
E.
licenseEnforced
Indicates that a license’s terms or restrictions are actively applied and upheld in relation to the associated entity or activity.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc664f099c8190be6d20a4574212ca |
completed | April 1, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.