Triple
T31568307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAE Hawk 127 |
E805479
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hawk family aircraft variant |
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: Hawk family aircraft variant Context triple: [BAE Hawk 127, instanceOf, Hawk family aircraft variant]
-
A.
aircraft variant family
chosen
A family of aircraft variants is a group of closely related aircraft models derived from a common base design, sharing core structures and systems but differing in specific configurations, capabilities, or roles.
-
B.
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.
-
C.
F-16 Fighting Falcon variant
A specific model or configuration of the F-16 Fighting Falcon multirole fighter aircraft, distinguished by particular avionics, structural features, performance characteristics, or mission capabilities.
-
D.
family of jet fighter aircraft
A family of jet fighter aircraft is a series of related high-performance military airplanes sharing a common design lineage, optimized for air-to-air and often air-to-ground combat roles.
-
E.
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.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:18 p.m.