Triple
T21772017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American A-5 Vigilante |
E537457
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cold War military aircraft |
C2492
|
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: Cold War military aircraft Context triple: [North American A-5 Vigilante, instanceOf, Cold War military aircraft]
-
A.
Cold War aviation concept
A Cold War aviation concept is a theoretical or proposed aircraft design, technology, or operational doctrine developed between roughly 1947 and 1991 to achieve strategic, tactical, or technological advantage within the era’s nuclear-armed, high-speed, and often clandestine military competition.
-
B.
World War II aircraft
World War II aircraft are military airplanes designed, produced, and deployed between 1939 and 1945 for roles such as fighters, bombers, transports, and reconnaissance in support of the war’s air operations.
-
C.
Soviet aircraft
Soviet aircraft are military and civilian airplanes and helicopters designed, produced, or operated by the Soviet Union, reflecting its technological, strategic, and industrial priorities from 1922 to 1991.
-
D.
military aircraft
chosen
A military aircraft is a powered flying vehicle specifically designed, equipped, and operated by armed forces to conduct combat, support, reconnaissance, or training missions in defense and warfare operations.
-
E.
Cold War military infrastructure
Cold War military infrastructure encompasses the global network of bases, missile silos, radar stations, command bunkers, communication systems, and logistical facilities built and maintained by rival blocs to support nuclear deterrence, rapid deployment, and continuous surveillance.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:51 p.m.