Triple
T26442893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AC-47 Spooky |
E665135
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variant of Douglas C-47 Skytrain |
C51575
|
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: variant of Douglas C-47 Skytrain Context triple: [AC-47 Spooky, instanceOf, variant of Douglas C-47 Skytrain]
-
A.
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.
-
B.
Lockheed Model 10 Electra variant
A Lockheed Model 10 Electra variant is a specific configuration of the twin‑engine, all‑metal monoplane airliner distinguished by modifications in equipment, performance, or role (such as transport, survey, or military use) from the standard Model 10 design.
-
C.
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.
-
D.
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.
-
E.
Convair 240 variant
A Convair 240 variant is a specific model within the Convair 240 family of twin‑engine, short- to medium-range airliners that incorporates design modifications or performance improvements over the original baseline aircraft.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:59 p.m.