Triple
T1636219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM Db2 |
E35363
|
entity |
| Predicate | supportsLicensingModel |
P8460
|
FINISHED |
| Object | per processor licensing |
—
|
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 processor licensing | Statement: [IBM Db2, supportsLicensingModel, per processor licensing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLicensingModel Context triple: [IBM Db2, supportsLicensingModel, per processor licensing]
-
A.
supportsLicense
Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
-
B.
licenseModel
chosen
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
-
C.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
-
D.
engineLicenseBasedOn
Indicates that an engine’s license is determined or derived from another specified license or licensing basis.
-
E.
supportsProduct
Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907cac610819083cafd4396b6d66c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.