Triple
T10345304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SF.260D |
E243729
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 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: aircraft variant Context triple: [SF.260D, instanceOf, aircraft variant]
-
A.
military trainer aircraft variant
chosen
A military trainer aircraft variant is a modified version of a standard military aircraft specifically adapted with dual controls, simplified systems, or performance changes to safely train pilots and aircrew in operational flying skills.
-
B.
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.
-
C.
light attack aircraft variant
A light attack aircraft variant is a modified version of a basic airframe optimized for low-cost, close air support, counterinsurgency, and limited strike missions with reduced payload and simpler systems compared to dedicated attack aircraft.
-
D.
Boeing 747 variant
A Boeing 747 variant is a specific model or configuration of the Boeing 747 airliner, distinguished by differences in size, range, engines, avionics, or interior layout tailored to particular airline or mission requirements.
-
E.
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.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:56 a.m.