Triple
T30050735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce TotalCare maintenance programs |
E763593
|
entity |
| Predicate | billingBasis |
P57372
|
FINISHED |
| Object | engine flying hours |
—
|
LITERAL FINISHED |
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: engine flying hours | Statement: [Rolls-Royce TotalCare maintenance programs, billingBasis, engine flying hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billingBasis Context triple: [Rolls-Royce TotalCare maintenance programs, billingBasis, engine flying hours]
-
A.
chargeBasis
Indicates the underlying reason, justification, or legal/contractual basis on which a charge, fee, or accusation is applied.
-
B.
billing
Indicates that one entity charges another entity for goods or services, typically by issuing an invoice or request for payment.
-
C.
billingGranularity
Indicates the level of detail or unit (such as per item, per hour, or per month) at which charges are calculated and presented in billing.
-
D.
chargesBasedOn
Indicates that one party determines or applies a fee, price, or cost to another party or item according to a specified basis, criterion, or reference.
-
E.
billingMetric
chosen
Indicates a relationship where a specific metric or measure is used as the basis for calculating billing or charges between entities.
- 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67a1567c0819095851e4b9a9c322b |
completed | May 2, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:55 p.m.