Triple
T28615329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Server and Client Access License |
E724259
|
entity |
| Predicate | hasLicensingMetric |
P188422
|
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: [Server and Client Access License, hasLicensingMetric, per user]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLicensingMetric Context triple: [Server and Client Access License, hasLicensingMetric, per user]
-
A.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
-
B.
usesLicensingModel
Indicates that one entity employs or applies a particular licensing model in its operations or offerings.
-
C.
hasLicenseCriteria
Indicates that an entity is subject to, or must satisfy, specific licensing requirements or conditions.
-
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. chosen
Provenance (4 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: April 28, 2026, 4:31 a.m.