Triple
T21239181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INVECS automatic transmission |
E523425
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mitsubishi proprietary technology |
C44417
|
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: Mitsubishi proprietary technology Context triple: [INVECS automatic transmission, instanceOf, Mitsubishi proprietary technology]
-
A.
Nissan technology
Nissan technology encompasses the innovative automotive systems, electric powertrains, safety features, and connectivity solutions developed by Nissan to enhance vehicle performance, efficiency, and driver experience.
-
B.
Nissan vehicle
A Nissan vehicle is a motorized transportation product manufactured by Nissan, encompassing a range of cars, trucks, and SUVs designed for personal or commercial use.
-
C.
Nissan engine
A Nissan engine is a power unit designed and manufactured by Nissan to convert fuel or electrical energy into mechanical power for propelling the vehicle and operating its systems.
-
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. 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:46 p.m.