Triple
T20515859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightning F.1 |
E503680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English Electric Lightning variant |
C43718
|
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: English Electric Lightning variant Context triple: [Lightning F.1, instanceOf, English Electric Lightning variant]
-
A.
Supermarine Swift variant
A Supermarine Swift variant is a specific model within the Supermarine Swift family of British jet fighter and reconnaissance aircraft, distinguished by particular modifications in design, equipment, or role.
-
B.
Gloster Meteor variant
A Gloster Meteor variant is a specific model or modification of the original British twin‑jet fighter, distinguished by changes in design, equipment, or role to meet particular operational requirements.
-
C.
Hawker Tempest variant
A Hawker Tempest variant is a specific model or sub-type of the British Hawker Tempest fighter aircraft distinguished by particular design features, performance characteristics, or operational roles.
-
D.
Bristol Blenheim variant
A Bristol Blenheim variant is a specific model or modification of the British twin‑engine light bomber and reconnaissance aircraft, distinguished by changes in features such as engines, armament, equipment, or airframe configuration.
-
E.
Hawker Hurricane variant
A Hawker Hurricane variant is a specific model or modification of the original British single-seat fighter aircraft, distinguished by changes in engine, armament, structure, or role to meet evolving operational requirements.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:36 a.m.