Triple
T30456649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-35 Lightning II |
E774881
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | carrier-capable aircraft variant family |
C28933
|
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: carrier-capable aircraft variant family Context triple: [F-35 Lightning II, instanceOf, carrier-capable aircraft variant family]
-
A.
aircraft variant family
A family of aircraft variants is a group of closely related aircraft models derived from a common base design, sharing core structures and systems but differing in specific configurations, capabilities, or roles.
-
B.
corporate aircraft family
A corporate aircraft family is a group of related business airplanes sharing common design features, performance characteristics, and brand lineage, tailored for executive and corporate travel needs.
-
C.
transport aircraft variant
A transport aircraft variant is a specific version of a transport airplane modified or configured for particular cargo, passenger, or mission requirements while retaining the core design of its base model.
-
D.
fighter aircraft family
A fighter aircraft family is a group of closely related combat aircraft variants that share a common airframe, design lineage, and core systems but differ in specific roles, capabilities, or configurations.
-
E.
carrier-based strike aircraft
chosen
A carrier-based strike aircraft is a naval combat airplane designed to operate from aircraft carriers and conduct precision attacks against surface, land, and maritime targets.
- F. None of above.
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_69f22494fb60819095d893de0284f886 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:10 p.m.