Triple
T30050710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce TotalCare maintenance programs |
E763593
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engine maintenance program |
C35743
|
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: engine maintenance program Context triple: [Rolls-Royce TotalCare maintenance programs, instanceOf, engine maintenance program]
-
A.
lighthouse maintenance program
A lighthouse maintenance program is a coordinated set of procedures, schedules, and resources dedicated to ensuring lighthouses remain structurally sound, operationally reliable, and compliant with safety and navigational standards.
-
B.
maintenance agency
A maintenance agency is an organization that provides ongoing repair, upkeep, and facility management services for buildings, equipment, or infrastructure on behalf of clients.
-
C.
certified pre-owned vehicle program
A certified pre-owned vehicle program is a manufacturer- or dealer-backed initiative that inspects, refurbishes, and warranties used vehicles to meet specific quality standards, offering buyers added assurance and benefits beyond typical used-car purchases.
-
D.
vehicle upgrade package
A vehicle upgrade package is a bundled set of optional enhancements—such as performance, comfort, technology, or aesthetic features—added to a base vehicle model to improve its capabilities or appeal.
-
E.
aircraft life extension program
chosen
An aircraft life extension program is a structured set of engineering, maintenance, and modification activities designed to safely extend an aircraft’s operational service life beyond its original design limits.
- 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.