Triple
T27840244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Hat Enterprise Agreement |
E703658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | enterprise software agreement |
C3153
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: enterprise software agreement Context triple: [Red Hat Enterprise Agreement, instanceOf, enterprise software agreement]
-
A.
enterprise software vendor
An enterprise software vendor is a company that develops, sells, and supports large-scale software solutions designed to meet the complex, mission-critical needs of organizations.
-
B.
enterprise software-as-a-service platform
An enterprise software-as-a-service platform is a cloud-based solution that delivers scalable, secure, and centrally managed business applications to organizations on a subscription basis.
-
C.
enterprise portal software
Enterprise portal software is a centralized, web-based platform that integrates applications, data, and services to provide personalized, secure access and collaboration tools for employees, partners, and customers across an organization.
-
D.
legal agreement
chosen
A legal agreement is a formally recognized arrangement between two or more parties that creates enforceable rights and obligations under the law.
-
E.
Microsoft licensing program
A Microsoft licensing program is a structured framework through which Microsoft offers, manages, and enforces the terms, pricing, and distribution of its software and cloud service licenses to organizations and individuals.
- F. None of above.
Provenance (1 batch)
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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 6:02 p.m.