Triple
T33924859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympus 201 |
E869720
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Rolls-Royce Olympus variant |
C59205
|
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: Rolls-Royce Olympus variant Context triple: [Olympus 201, instanceOf, Rolls-Royce Olympus variant]
-
A.
Rolls-Royce Avon variant
The Rolls-Royce Avon variant is a specific model within the Avon family of axial-flow turbojet engines, distinguished by tailored performance characteristics, configurations, or applications for particular aircraft or operational requirements.
-
B.
Merlin engine variant
A Merlin engine variant is a specific configuration or model within the Merlin family of liquid-fueled rocket engines, distinguished by tailored performance characteristics, design modifications, or mission-specific optimizations.
-
C.
Pratt & Whitney R-2800
The Pratt & Whitney R-2800 is an 18-cylinder, air-cooled, twin-row radial aircraft engine widely used in World War II and early postwar military and civilian aircraft for its high power and reliability.
-
D.
Hawker Siddeley Trident variant
A Hawker Siddeley Trident variant is a specific model within the Trident family of British-built, three-engined jet airliners, distinguished by particular design modifications, performance characteristics, and operational roles.
-
E.
H-24 engine
An H-24 engine is a 24-cylinder internal combustion engine arranged in an "H" configuration, effectively combining two horizontally opposed 12-cylinder engines to drive a common output shaft.
- F. None of above. chosen
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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.