Triple
T31024981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-21 |
E790544
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reconnaissance aircraft variant |
C4000
|
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: reconnaissance aircraft variant Context triple: [M-21, instanceOf, reconnaissance aircraft variant]
-
A.
reconnaissance aircraft
chosen
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.
-
B.
bomber aircraft variant
A bomber aircraft variant is a specific version of a bomber designed or modified to perform particular roles, missions, or operate under distinct performance, payload, or technological configurations.
-
C.
transport aircraft variant
A transport aircraft variant is a specific version of a transport airplane modified or configured for particular cargo, passenger, or mission requirements while retaining the core design of its base model.
-
D.
maritime patrol aircraft variant
A maritime patrol aircraft variant is a specialized version of an aircraft configured and equipped for long-endurance surveillance, anti-submarine warfare, and maritime security operations over sea areas.
-
E.
Lockheed Hudson variant
A Lockheed Hudson variant is a specific model or modification of the Lockheed Hudson twin‑engine light bomber and maritime patrol aircraft, distinguished by particular equipment, performance characteristics, or mission adaptations.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:58 p.m.