Triple
T27507796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond DA40‑180 |
E694324
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Diamond DA40 variant |
C52860
|
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: Diamond DA40 variant Context triple: [Diamond DA40‑180, instanceOf, Diamond DA40 variant]
-
A.
Beechcraft Baron variant
A Beechcraft Baron variant is a specific model or configuration within the Baron family of twin‑engine light aircraft, distinguished by particular performance, equipment, or design features.
-
B.
Hawker 800 variant
The Hawker 800 variant is a mid-size business jet model within the Hawker 800 series, distinguished by specific performance, avionics, or interior configuration differences tailored to particular operational or customer requirements.
-
C.
Gulfstream V variant
A Gulfstream V variant is a specific model or configuration of the long-range, large-cabin Gulfstream V business jet, modified to meet particular performance, mission, or customer requirements.
-
D.
Learjet 35 variant
A Learjet 35 variant is a specific model or modification of the Learjet 35 light business jet, distinguished by changes in performance, configuration, or equipment to suit particular operational roles or customer requirements.
-
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. chosen
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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:14 p.m.