Triple
T21146056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z34 |
E521057
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nissan internal chassis code |
C44605
|
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: Nissan internal chassis code Context triple: [Z34, instanceOf, Nissan internal chassis code]
-
A.
Lexus internal chassis code
A Lexus internal chassis code is a manufacturer-assigned alphanumeric identifier that designates a specific Lexus vehicle platform, generation, and major mechanical configuration for engineering and cataloging purposes.
-
B.
Toyota chassis code
A Toyota chassis code is an alphanumeric identifier used by Toyota to specify a vehicle’s platform, engine type, drivetrain, and generation for classification and parts/reference purposes.
-
C.
BMW internal model code
A BMW internal model code is a manufacturer-assigned alphanumeric identifier used within BMW to uniquely designate a specific vehicle platform, generation, or variant for engineering, production, and cataloging purposes.
-
D.
Mercedes-Benz chassis code
A Mercedes-Benz chassis code is an alphanumeric designation used by the manufacturer to identify the specific platform, body style, and generation of a Mercedes-Benz vehicle.
-
E.
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.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:58 p.m.