Triple
T30707993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PW5000 |
E781805
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | turbofan engine development designation |
C7677
|
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: turbofan engine development designation Context triple: [PW5000, instanceOf, turbofan engine development designation]
-
A.
military jet engine designation
A military jet engine designation is a standardized alphanumeric code that uniquely identifies a specific model and variant of a jet engine used in military aircraft, indicating its type, series, and sometimes its manufacturer or performance characteristics.
-
B.
turbofan engine
chosen
A turbofan engine is a type of air-breathing jet engine that uses a large fan driven by a gas turbine to produce thrust through both accelerated bypass air and exhaust gases for efficient high-speed propulsion.
-
C.
afterburning turbofan engine
An afterburning turbofan engine is a type of jet engine that combines a turbofan’s efficient core and bypass airflow with an additional combustion stage in the exhaust (afterburner) to provide short-term, significantly increased thrust, typically for military aircraft.
-
D.
aircraft engine family
A family of aircraft engines is a group of closely related engine models that share a common core design, architecture, and components but differ in specific configurations, performance levels, or applications.
-
E.
aircraft designation
An aircraft designation is a standardized alphanumeric code that identifies an aircraft’s type, role, and variant within a specific classification system.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:35 p.m.