Triple
T27840246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Hat Enterprise Agreement |
E703658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subscription 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: subscription agreement Context triple: [Red Hat Enterprise Agreement, instanceOf, subscription agreement]
-
A.
subscription service
A subscription service is a business model where customers pay a recurring fee at regular intervals to gain continuous access to products, services, or content.
-
B.
subscription library
A subscription library is a service where members pay recurring fees to access a curated collection of books, media, or digital resources, often with borrowing privileges and additional member benefits.
-
C.
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.
-
D.
subscription management service
A subscription management service is a system that automates the creation, billing, modification, and cancellation of recurring customer subscriptions while tracking usage, payments, and plan details.
-
E.
partnership agreement
A partnership agreement is a legally binding contract between two or more parties that defines their business relationship, including ownership shares, roles, responsibilities, profit and loss distribution, and procedures for decision-making and dispute resolution.
- 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.