Triple
T31356883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAC Mustang |
E799760
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | P-51 Mustang variant |
C57450
|
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: P-51 Mustang variant Context triple: [CAC Mustang, instanceOf, P-51 Mustang variant]
-
A.
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.
-
B.
Hawker Hurricane variant
A Hawker Hurricane variant is a specific model or modification of the original British single-seat fighter aircraft, distinguished by changes in engine, armament, structure, or role to meet evolving operational requirements.
-
C.
Lockheed Constellation variant
A Lockheed Constellation variant is a specific model within the Constellation family of four‑engined, propeller‑driven airliners and military transports, distinguished by particular structural, performance, or role-related modifications.
-
D.
Boeing B-17 variant
A Boeing B-17 variant is a specific model or modification of the B-17 Flying Fortress bomber, distinguished by changes in design, equipment, performance, or mission role.
-
E.
de Havilland Mosquito variant
A de Havilland Mosquito variant is a specific model of the twin‑engine, multi‑role World War II aircraft distinguished by particular modifications to its structure, equipment, or mission profile (such as fighter, bomber, reconnaissance, or night fighter roles).
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:17 p.m.