Triple
T33652635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comet 4C |
E862138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | de Havilland Comet variant |
C58394
|
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: de Havilland Comet variant Context triple: [Comet 4C, instanceOf, de Havilland Comet variant]
-
A.
Hawker Siddeley Trident variant
A Hawker Siddeley Trident variant is a specific model within the Trident family of British-built, three-engined jet airliners, distinguished by particular design modifications, performance characteristics, and operational roles.
-
B.
Handley Page Halifax variant
A Handley Page Halifax variant is a specific model or modification of the British four‑engined heavy bomber, distinguished by changes in engines, armament, structure, or equipment to fulfill particular operational roles during its service life.
-
C.
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.
-
D.
Lockheed Constellation variant
A Lockheed Constellation variant is a specific model within the Constellation family of four‑engined, propeller‑driven airliners and military transports, distinguished by particular structural, performance, or role-related modifications.
-
E.
Convair 240 variant
A Convair 240 variant is a specific model within the Convair 240 family of twin‑engine, short- to medium-range airliners that incorporates design modifications or performance improvements over the original baseline aircraft.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.