Triple
T38401741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce 250-C20W |
E900916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Rolls-Royce Model 250 variant |
C63605
|
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 Model 250 variant Context triple: [Rolls-Royce 250-C20W, instanceOf, Rolls-Royce Model 250 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.
Bristol Blenheim variant
A Bristol Blenheim variant is a specific model or modification of the British twin‑engine light bomber and reconnaissance aircraft, distinguished by changes in features such as engines, armament, equipment, or airframe configuration.
-
C.
Handley Page Victor variant
A Handley Page Victor variant is a specific model or modification of the British Handley Page Victor jet-powered strategic bomber and tanker aircraft, distinguished by changes in design, equipment, or role.
-
D.
Armstrong Whitworth Whitley variant
The Armstrong Whitworth Whitley variant is a specific model or modification of the British twin-engine, long-range heavy bomber aircraft used primarily by the Royal Air Force during the early years of World War II.
-
E.
Rolls-Royce Olympus variant
A Rolls-Royce Olympus variant is a specific model within the Olympus family of axial-flow turbojet or turbofan engines, distinguished by tailored design modifications to meet particular aircraft, marine, or industrial performance and installation requirements.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.