Triple
T29310970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fighter, Attack and Reconnaissance 39 |
E743231
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multirole combat aircraft role |
C48653
|
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: multirole combat aircraft role Context triple: [Fighter, Attack and Reconnaissance 39, instanceOf, multirole combat aircraft role]
-
A.
military aviation role
chosen
A military aviation role is a specific function or mission type assigned to aircraft and aircrew within armed forces, such as air superiority, ground attack, reconnaissance, transport, or electronic warfare.
-
B.
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.
-
C.
military aircraft
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.
-
D.
carrier-based strike aircraft
A carrier-based strike aircraft is a naval combat airplane designed to operate from aircraft carriers and conduct precision attacks against surface, land, and maritime targets.
-
E.
military aircraft requirement
A military aircraft requirement is a formal, testable specification that defines the necessary capabilities, performance, and constraints an aircraft must meet to fulfill designated military missions and operational needs.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:16 p.m.