Triple
T28899731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Software Components Group |
E732920
|
entity |
| Predicate | productLicenseModel |
P8460
|
FINISHED |
| Object | commercial proprietary license |
—
|
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: commercial proprietary license | Statement: [Software Components Group, productLicenseModel, commercial proprietary license]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productLicenseModel Context triple: [Software Components Group, productLicenseModel, commercial proprietary license]
-
A.
licenseOfProduct
Indicates that a specified license applies to, governs, or is associated with a particular product.
-
B.
licenseModel
chosen
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
-
C.
usesLicensingModel
Indicates that one entity employs or applies a particular licensing model in its operations or offerings.
-
D.
previousLicenseModel
Indicates that an entity was governed by a different license model before the current one.
-
E.
licensedProductType
Indicates the type or category of product for which a license has been granted.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 28, 2026, 8:01 a.m.