Triple
T29310968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fighter, Attack and Reconnaissance 39 |
E743231
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aircraft role designation |
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: aircraft role designation Context triple: [Fighter, Attack and Reconnaissance 39, instanceOf, aircraft role designation]
-
A.
aircraft designation
An aircraft designation is a standardized alphanumeric code that identifies an aircraft’s type, role, and variant within a specific classification system.
-
B.
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.
-
C.
aircraft designation prefix
An aircraft designation prefix is a standardized code or letter sequence placed before an aircraft’s model number to indicate its primary role, function, or configuration (e.g., fighter, transport, trainer).
-
D.
military aircraft nickname
A military aircraft nickname is an informal or semi-official moniker given to a specific aircraft model or type, often reflecting its appearance, role, performance, or reputation among service members and the public.
-
E.
reconnaissance aircraft
A reconnaissance aircraft is a specialized military or intelligence-gathering airplane designed to observe, monitor, and collect information about enemy forces, terrain, or strategic targets using advanced sensors and surveillance equipment.
- 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.