Triple
T37268939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Custom Vehicle Operations |
E924461
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Harley-Davidson division |
C30005
|
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: Harley-Davidson division Context triple: [Custom Vehicle Operations, instanceOf, Harley-Davidson division]
-
A.
motorcycle manufacturer division
chosen
A motorcycle manufacturer division is an organizational unit within a company responsible for the design, production, marketing, and distribution of motorcycles and related products.
-
B.
Harley-Davidson engine
A Harley-Davidson engine is a distinctive V-twin internal combustion powerplant designed by Harley-Davidson, characterized by its unique sound, strong low-end torque, and iconic styling used to power the brand’s motorcycles.
-
C.
Kawasaki Heavy Industries division
A Kawasaki Heavy Industries division is an organizational unit within the multinational corporation responsible for managing specific product lines or business areas such as aerospace, rolling stock, shipbuilding, energy systems, or industrial equipment.
-
D.
Bosch division
A Bosch division is a major organizational unit within the Bosch Group that focuses on a specific business area, such as mobility solutions, industrial technology, consumer goods, or energy and building technology, with its own strategy, products, and operations.
-
E.
motorcycle marque
A motorcycle marque is a brand or manufacturer name under which motorcycles are designed, produced, and marketed, often associated with a distinct heritage, style, and engineering philosophy.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.