Triple
T20667739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightning T.5 |
E507936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trainer aircraft variant |
C39065
|
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: trainer aircraft variant Context triple: [Lightning T.5, instanceOf, trainer aircraft variant]
-
A.
military trainer aircraft variant
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.
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.
-
C.
bomber aircraft variant
A bomber aircraft variant is a specific version of a bomber designed or modified to perform particular roles, missions, or operate under distinct performance, payload, or technological configurations.
-
D.
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.
-
E.
aircraft variant name
chosen
A specific designation that distinguishes a particular version or configuration of an aircraft model, reflecting differences in design, performance, equipment, or role.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:44 a.m.