Triple
T5579514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McDonnell Douglas Phantom FGR.2 |
E146606
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 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: F-4 Phantom II variant Context triple: [McDonnell Douglas Phantom FGR.2, instanceOf, F-4 Phantom II variant]
-
A.
X-plane
An X-plane is an experimental aircraft designed to test and demonstrate new aviation technologies, configurations, or performance capabilities beyond those of conventional aircraft.
-
B.
Boeing 707 derivative
A Boeing 707 derivative is any aircraft model developed from the original Boeing 707 airframe, incorporating modifications such as structural changes, updated systems, or specialized configurations while retaining its core design lineage.
-
C.
Boeing 747 variant
A Boeing 747 variant is a specific model or configuration of the Boeing 747 airliner, distinguished by differences in size, range, engines, avionics, or interior layout tailored to particular airline or mission requirements.
-
D.
variant of Lockheed Martin F-35 Lightning II
A variant of the Lockheed Martin F-35 Lightning II is a specific configuration of the fifth-generation multirole stealth fighter tailored to distinct mission profiles, service branches, or export requirements while retaining the core airframe, avionics, and low-observable characteristics.
-
E.
Messerschmitt Me 262 variant
A Messerschmitt Me 262 variant is a specific model or modification of the German World War II jet fighter, distinguished by changes in armament, engines, airframe, or operational role.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:37 p.m.