Triple
T16181303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honda Marine |
E392688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of Honda Motor Company |
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: division of Honda Motor Company Context triple: [Honda Marine, instanceOf, division of Honda Motor Company]
-
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.
division of BMW
A division of BMW is an organizational unit within the BMW Group responsible for a specific product line, market segment, or business function, such as BMW, MINI, or BMW Motorrad.
-
C.
Honda executive
A Honda executive is a high-level decision-maker responsible for guiding the company’s strategic direction, overseeing operations and innovation, and ensuring sustainable growth in alignment with Honda’s global vision and values.
-
D.
Toyota Motor Corporation facility
A Toyota Motor Corporation facility is any physical site owned or operated by Toyota where activities such as vehicle manufacturing, research and development, logistics, administration, sales, or service are conducted in support of the company’s automotive business.
-
E.
Toyota subsidiary
A Toyota subsidiary is a legally distinct company in which Toyota Motor Corporation holds a controlling interest, operating under its strategic direction while managing specific regional markets, product lines, or business functions.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:02 a.m.