Triple
T17364635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EF-2000 Typhoon |
E422155
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eurofighter Typhoon |
C38480
|
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: Eurofighter Typhoon Context triple: [EF-2000 Typhoon, instanceOf, Eurofighter Typhoon]
-
A.
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.
-
B.
Dassault Mirage III variant
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.
-
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.
Hawker Tempest variant
A Hawker Tempest variant is a specific model or sub-type of the British Hawker Tempest fighter aircraft distinguished by particular design features, performance characteristics, or operational roles.
-
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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.