Triple
T28618534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remote Desktop Licensing |
E724325
|
entity |
| Predicate | licenseProgram |
P167921
|
FINISHED |
| Object | Enterprise Agreement |
—
|
NE NERFINISHED |
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: Enterprise Agreement | Statement: [Remote Desktop Licensing, licenseProgram, Enterprise Agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseProgram Context triple: [Remote Desktop Licensing, licenseProgram, Enterprise Agreement]
-
A.
licenseName
Indicates the specific name or title of the license under which an entity is provided or governed.
-
B.
licenseFocus
Indicates that a license specifically targets, applies to, or is primarily concerned with a particular subject, activity, or scope.
-
C.
licenseModel
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
-
D.
licenseFamily
Indicates that one license belongs to, is derived from, or is categorized under a broader family or class of related licenses.
-
E.
licenseOfProduct
Indicates that a specified license applies to, governs, or is associated with a particular product.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f66e5f7e30819094530abceabd5f43 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 4:32 a.m.