Triple
T9692144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-50 AWACS |
E234561
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian 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: Russian military aircraft Context triple: [A-50 AWACS, instanceOf, Russian military aircraft]
-
A.
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.
-
B.
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.
-
C.
Soviet military equipment
Soviet military equipment encompasses the weapons, vehicles, and support systems designed and produced by the Soviet Union to equip its armed forces, characterized by rugged construction, mass production, and doctrinal emphasis on large-scale, combined-arms warfare.
-
D.
fighter aircraft
A fighter aircraft is a fast, highly maneuverable military airplane designed primarily to secure air superiority by engaging and destroying enemy aircraft in combat.
-
E.
component of the Soviet Air Forces
A component of the Soviet Air Forces is an organizational unit, formation, or specialized element (such as a regiment, division, or support service) that collectively contributed to the operational, logistical, and strategic capabilities of the USSR’s military aviation.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:17 p.m.