Triple
T24480059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HC-131 Samaritan |
E617346
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military transport aircraft variant |
C44112
|
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: military transport aircraft variant Context triple: [HC-131 Samaritan, instanceOf, military transport aircraft variant]
-
A.
transport aircraft variant
chosen
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.
-
B.
strategic airlifter
A strategic airlifter is a large military transport aircraft designed to carry heavy cargo, troops, and equipment over long distances to support global deployment and sustainment operations.
-
C.
military trainer aircraft variant
A military trainer aircraft variant is a modified version of a standard military aircraft specifically adapted with dual controls, simplified systems, or performance changes to safely train pilots and aircrew in operational flying skills.
-
D.
bomber aircraft variant
A bomber aircraft variant is a specific version of a bomber designed or modified to perform particular roles, missions, or operate under distinct performance, payload, or technological configurations.
-
E.
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.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:21 a.m.