Triple
T35871392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S 32C reconnaissance variant |
E1037234
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Saab 32 Lansen variant |
C32944
|
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: Saab 32 Lansen variant Context triple: [S 32C reconnaissance variant, instanceOf, Saab 32 Lansen variant]
-
A.
variant of Saab 32 Lansen
chosen
A variant of the Saab 32 Lansen is a specific model or configuration of the Swedish twin-seat, jet-powered attack aircraft, modified for distinct roles such as strike, reconnaissance, or electronic warfare.
-
B.
Panavia Tornado variant
A Panavia Tornado variant is a specific model of the multirole combat aircraft tailored with distinct avionics, structural modifications, and mission equipment to fulfill specialized roles such as strike, reconnaissance, or air defense.
-
C.
Dassault Mirage III variant
A Dassault Mirage III variant is a specific model within the Mirage III family of French supersonic jet fighters, distinguished by tailored modifications in avionics, engines, armament, or mission role to meet particular operational or export requirements.
-
D.
Su-30 variant
A Su-30 variant is a specific model within the Su-30 family of twin-engine, multirole fighter aircraft, distinguished by customized avionics, weapons systems, and structural modifications tailored to the requirements of a particular operator or mission profile.
-
E.
Learjet 35 variant
A Learjet 35 variant is a specific model or modification of the Learjet 35 light business jet, distinguished by changes in performance, configuration, or equipment to suit particular operational roles or customer requirements.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.