Triple
T37756332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RF-4E |
E941123
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | McDonnell Douglas F-4 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 F-4 Phantom II variant Context triple: [RF-4E, instanceOf, McDonnell Douglas F-4 Phantom II variant]
-
A.
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.
-
B.
F-15 Eagle variant
A specific model or modification of the McDonnell Douglas F-15 Eagle air superiority fighter, distinguished by tailored avionics, structural changes, or mission equipment to fulfill specialized operational roles.
-
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.
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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:19 p.m.