Triple
T28998030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multiple Virtual Storage |
E736218
|
entity |
| Predicate | vendorSupport |
P48616
|
FINISHED |
| Object | IBM Global Services |
—
|
NE NERFINISHED |
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: IBM Global Services | Statement: [Multiple Virtual Storage, vendorSupport, IBM Global Services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vendorSupport Context triple: [Multiple Virtual Storage, vendorSupport, IBM Global Services]
-
A.
vendorSupportStatus
Indicates the current level or state of support provided by a vendor for a product, service, or customer.
-
B.
supportedIn
chosen
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
C.
supportsVendor
Indicates that one entity provides assistance, resources, or endorsement to a vendor in carrying out its activities or services.
-
D.
supportsHardwareVendor
Indicates that one entity provides assistance, resources, or endorsement to a hardware vendor in fulfilling its products or services.
-
E.
tieneSoporte
Indicates that one entity provides support, backing, or a supporting structure for another entity.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fb8003081909d0e3ee34237bc29 |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:32 a.m.