Triple
T15171472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cent Studio |
E362494
|
entity |
| Predicate | productLicense |
P8460
|
FINISHED |
| Object | proprietary freeware |
—
|
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: proprietary freeware | Statement: [Cent Studio, productLicense, proprietary freeware]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productLicense Context triple: [Cent Studio, productLicense, proprietary freeware]
-
A.
licensedProductType
Indicates the type or category of product for which a license has been granted.
-
B.
supportsLicense
Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
-
C.
licenseFor
Indicates that one entity grants or holds formal permission or authorization for another entity to perform an activity, use a resource, or operate under specified conditions.
-
D.
licenseModel
chosen
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
-
E.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0064ec56481909f11fa6e5686f076 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.