Triple
T36380945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MC-130J Commando II |
E896044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lockheed Martin C-130 variant |
C65731
|
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 Martin C-130 variant Context triple: [MC-130J Commando II, instanceOf, Lockheed Martin C-130 variant]
-
A.
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.
-
B.
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.
-
C.
variant of Douglas C-47 Skytrain
A variant of the Douglas C-47 Skytrain is a specific modified version of this military transport aircraft, distinguished by changes in equipment, configuration, or performance to fulfill specialized operational roles.
-
D.
AC-130 gunship variant
A heavily armed, fixed-wing ground-attack aircraft variant of the AC-130 gunship, optimized for persistent close air support, air interdiction, and armed reconnaissance using side-firing cannons, autocannons, and precision-guided munitions.
-
E.
F-111 variant
An F-111 variant is a specific model or modification of the General Dynamics F-111 Aardvark aircraft, distinguished by unique design features, roles, or performance characteristics.
- 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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.