Triple
T20703831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAC One-Eleven (re-engined variants) |
E508847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aircraft variant family |
C43470
|
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 variant family Context triple: [BAC One-Eleven (re-engined variants), instanceOf, aircraft variant family]
-
A.
aircraft variant name
A specific designation that distinguishes a particular version or configuration of an aircraft model, reflecting differences in design, performance, equipment, or role.
-
B.
bomber aircraft variant
A bomber aircraft variant is a specific version of a bomber designed or modified to perform particular roles, missions, or operate under distinct performance, payload, or technological configurations.
-
C.
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.
-
D.
fighter aircraft family
A fighter aircraft family is a group of closely related combat aircraft variants that share a common airframe, design lineage, and core systems but differ in specific roles, capabilities, or configurations.
-
E.
corporate aircraft family
A corporate aircraft family is a group of related business airplanes sharing common design features, performance characteristics, and brand lineage, tailored for executive and corporate travel needs.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 12:13 p.m.