Triple
T9804713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SF.260 Warrior |
E237925
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military trainer aircraft variant |
C26861
|
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: military trainer aircraft variant Context triple: [SF.260 Warrior, instanceOf, military trainer aircraft variant]
-
A.
jet trainer aircraft
A jet trainer aircraft is a small, high-performance jet-powered airplane designed to train pilots in advanced flying skills, including high-speed handling, navigation, and combat or tactical maneuvers, before they transition to frontline operational aircraft.
-
B.
MiG-29 derivative
A MiG-29 derivative is any aircraft design or variant that evolves from the original MiG-29 Fulcrum platform, incorporating modifications in structure, avionics, propulsion, or mission role while retaining its core aerodynamic and design lineage.
-
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.
single‑engine fighter aircraft
A single-engine fighter aircraft is a fast, maneuverable military airplane powered by one engine and designed primarily for air-to-air combat and limited ground-attack missions.
-
E.
stretched airliner variant
A stretched airliner variant is a lengthened version of an existing aircraft model, typically achieved by adding fuselage sections to increase passenger or cargo capacity while retaining most of the original design and systems.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:29 p.m.