Triple
T18004243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FB-111 Aardvark |
E430703
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | F-111 variant |
C40278
|
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: F-111 variant Context triple: [FB-111 Aardvark, instanceOf, F-111 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.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- F. None of above. chosen
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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:23 a.m.