Triple
T34236973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lion III |
E878362
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Napier Lion engine variant |
C58742
|
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: Napier Lion engine variant Context triple: [Lion III, instanceOf, Napier Lion engine 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.
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.
-
C.
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.
-
D.
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.
-
E.
Napier Lion variant
chosen
The Napier Lion variant is a specific model or modification of the Napier Lion aircraft engine, distinguished by particular design features, performance characteristics, or intended applications.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:56 a.m.