Triple
T14645199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirage IIIR |
E343827
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mirage III variant |
C33511
|
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: Mirage III variant Context triple: [Mirage IIIR, instanceOf, Mirage III variant]
-
A.
Dassault Mirage III variant
chosen
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.
-
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.
McDonnell F-101 Voodoo variant
A McDonnell F-101 Voodoo variant is a specific model within the F-101 family of supersonic jet fighters and reconnaissance aircraft, distinguished by particular modifications in role, avionics, armament, or structural configuration.
-
D.
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.
-
E.
F-4 Phantom II variant
A specific model or modification of the McDonnell Douglas F-4 Phantom II fighter-bomber, distinguished by particular avionics, structural changes, or mission equipment tailored to specific operational roles or users.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:26 a.m.