Triple
T38454124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T53-L-13 |
E912260
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lycoming T53 engine variant |
C63458
|
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: Lycoming T53 engine variant Context triple: [T53-L-13, instanceOf, Lycoming T53 engine variant]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Lockheed Hudson variant
A Lockheed Hudson variant is a specific model or modification of the Lockheed Hudson twin‑engine light bomber and maritime patrol aircraft, distinguished by particular equipment, performance characteristics, or mission adaptations.
-
E.
Cessna T‑41 variant
The Cessna T‑41 variant is a military training and liaison aircraft derived from the Cessna 172, adapted with specialized avionics and equipment for pilot instruction and utility roles.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:31 p.m.