Triple
T28618521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remote Desktop Licensing |
E724325
|
entity |
| Predicate | supportsLicensingMode |
P50497
|
FINISHED |
| Object | Per User |
—
|
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: Per User | Statement: [Remote Desktop Licensing, supportsLicensingMode, Per User]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLicensingMode Context triple: [Remote Desktop Licensing, supportsLicensingMode, Per User]
-
A.
usesLicensingModel
chosen
Indicates that one entity employs or applies a particular licensing model in its operations or offerings.
-
B.
supportsLicense
Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
-
C.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
-
D.
typeOfLicensingItManaged
Indicates that one entity manages or oversees the licensing arrangements or permissions associated with another entity.
-
E.
hasLicensingMetric
Indicates that one entity uses another entity as the metric or basis for determining licensing terms or conditions.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a017d27e184819094638c3cf6876de4 |
completed | May 11, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_6a017c785a44819083111384b55769e9 |
completed | May 11, 2026, 6:51 a.m. |
Created at: April 28, 2026, 4:32 a.m.