Triple
T21555002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FGR.2 |
E531867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | McDonnell Douglas Phantom II variant |
C19283
|
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: McDonnell Douglas Phantom II variant Context triple: [FGR.2, instanceOf, McDonnell Douglas Phantom II variant]
-
A.
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.
-
B.
Convair 240 variant
A Convair 240 variant is a specific model within the Convair 240 family of twin‑engine, short- to medium-range airliners that incorporates design modifications or performance improvements over the original baseline aircraft.
-
C.
F-4 Phantom II variant
chosen
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.
-
D.
Douglas A-4 Skyhawk variant
A Douglas A-4 Skyhawk variant is a specific model within the A-4 family of carrier-capable, single-seat, subsonic light attack aircraft, distinguished by particular modifications in avionics, structure, or mission equipment.
-
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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:29 p.m.