Triple
T6214327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce aircraft engines |
E138947
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aircraft engine family |
C19429
|
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: aircraft engine family Context triple: [Rolls-Royce aircraft engines, instanceOf, aircraft engine family]
-
A.
automotive engine family
An automotive engine family is a group of closely related internal combustion engines that share a common basic design, architecture, and components but differ in specific parameters such as displacement, tuning, or fuel system to suit various vehicle applications.
-
B.
automobile engine family
A group of related automobile engines that share a common design architecture, components, and core specifications, but may vary in displacement, tuning, or configuration to suit different vehicles or performance requirements.
-
C.
automobile engine family
A group of related automobile engines that share a common design architecture, components, and engineering characteristics, often varying only in displacement, tuning, or minor features.
-
D.
engine family
An engine family is a group of related internal combustion engines that share a common basic design, architecture, and components but may differ in specific configurations, displacements, or performance characteristics.
-
E.
diesel engine family
A diesel engine family is a group of related diesel engines that share a common basic design, architecture, and components but differ in specific configurations such as displacement, power output, and intended applications.
- 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_69c008ada364819096c9e92c74d639b5 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:21 p.m.