Triple
T27254447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell YOH-4 |
E687573
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prototype helicopter |
C52665
|
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: prototype helicopter Context triple: [Bell YOH-4, instanceOf, prototype helicopter]
-
A.
helicopter concept
A helicopter concept is an abstract representation of a rotary-wing aircraft’s essential characteristics, including its structure, propulsion, control systems, and operational capabilities, independent of any specific physical instance.
-
B.
piston-powered helicopter
A piston-powered helicopter is a rotary-wing aircraft whose main rotor is driven by one or more reciprocating (piston) engines, typically used for light-duty, training, or private operations due to their lower cost and complexity compared to turbine-powered helicopters.
-
C.
twin-engine helicopter
A twin-engine helicopter is a rotary-wing aircraft equipped with two independent engines that provide increased power, redundancy, and safety for missions such as transport, search and rescue, and offshore operations.
-
D.
twin-engine helicopter
A twin-engine helicopter is a rotary-wing aircraft equipped with two independent engines that provide increased power, redundancy, and safety for transporting passengers or cargo.
-
E.
twin‑engine helicopter
A twin-engine helicopter is a rotary-wing aircraft equipped with two independent engines that provide increased power, redundancy, and safety for missions such as transport, search and rescue, and offshore operations.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 10:48 a.m.