Triple
T30050712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce TotalCare maintenance programs |
E763593
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-term service 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: long-term service agreement Context triple: [Rolls-Royce TotalCare maintenance programs, instanceOf, long-term service agreement]
-
A.
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.
-
B.
operating rights agreement
An operating rights agreement is a contractual arrangement that grants a party the authority to operate, manage, or use specific assets, facilities, or services under defined terms, conditions, and limitations.
-
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.
environmental management agreement
An environmental management agreement is a formal arrangement between parties that outlines responsibilities, actions, and standards for protecting, managing, or improving environmental resources and impacts.
-
E.
extension service organization
An extension service organization is an institution that provides education, resources, and technical assistance to individuals and communities—often in agriculture, health, or community development—to help them apply research-based knowledge in practical ways.
- 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 6:55 p.m.