Triple
T36796528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AP-2H |
E909198
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lockheed P2V Neptune variant |
C65897
|
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: Lockheed P2V Neptune variant Context triple: [AP-2H, instanceOf, Lockheed P2V Neptune variant]
-
A.
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.
-
B.
Douglas A-4 Skyhawk variant
A Douglas A-4 Skyhawk variant is a specific model within the A-4 family of carrier-capable, single-seat, subsonic light attack aircraft, distinguished by particular modifications in avionics, structure, or mission equipment.
-
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.
Boeing C-97 Stratofreighter variant
A Boeing C-97 Stratofreighter variant is a specific model derived from the original C-97 military transport aircraft, modified for specialized roles such as aerial refueling, passenger transport, or other mission-specific purposes.
-
E.
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.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.