Triple
T17598766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MySQL AB |
E428638
|
entity |
| Predicate | licenseManagedForProduct |
P37651
|
FINISHED |
| Object | commercial MySQL licenses |
—
|
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 MySQL licenses | Statement: [MySQL AB, licenseManagedForProduct, commercial MySQL licenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseManagedForProduct Context triple: [MySQL AB, licenseManagedForProduct, commercial MySQL licenses]
-
A.
licensedProductType
Indicates the type or category of product for which a license has been granted.
-
B.
typeOfLicensingItManaged
chosen
Indicates that one entity manages or oversees the licensing arrangements or permissions associated with another entity.
-
C.
licenseManufacturerOf
Indicates that one entity is authorized, via a license, to manufacture products or goods on behalf of or under the rights of another entity.
-
D.
licenseEnforced
Indicates that a license’s terms or restrictions are actively applied and upheld in relation to the associated entity or activity.
-
E.
licenseStatus
Indicates the current state or condition of a license in relation to its validity, permissions, or compliance.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c474e5481909d2736241b592dab |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.