Triple
T10033223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM Power Systems |
E204899
|
entity |
| Predicate | supportsCloudModel |
P92016
|
FINISHED |
| Object | on-premises deployment |
—
|
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: on-premises deployment | Statement: [IBM Power Systems, supportsCloudModel, on-premises deployment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCloudModel Context triple: [IBM Power Systems, supportsCloudModel, on-premises deployment]
-
A.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
-
B.
supportsModelVariant
Indicates that one entity is capable of operating with, being compatible with, or otherwise accommodating a specific variant of a model.
-
C.
supportsModelFamily
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or use of a particular model family.
-
D.
hasCloudComposition
Indicates that an atmospheric body or region possesses a specific composition or makeup of clouds.
-
E.
supportsCloudImages
Indicates that an entity is capable of handling, displaying, or otherwise working with images stored or managed in a cloud environment.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce47845c8190ab5696267fdedcad |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 8:54 p.m.