Triple
T30142942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Typ 8R |
E766175
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Audi internal model designation |
C54966
|
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: Audi internal model designation Context triple: [Typ 8R, instanceOf, Audi internal model designation]
-
A.
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.
-
B.
Nissan internal chassis code
A Nissan internal chassis code is a manufacturer-assigned alphanumeric identifier used to distinguish specific vehicle platforms, generations, and configurations within Nissan’s product lineup.
-
C.
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.
-
D.
Formula One chassis designation
A Formula One chassis designation is the unique alphanumeric identifier assigned by a team to a specific car design or iteration, used to distinguish it from other models across seasons and within the same year.
-
E.
Audi A4 generation
chosen
An Audi A4 generation represents a distinct production series of the Audi A4 model, defined by a specific platform, design language, technology set, and mechanical configuration produced over a particular time span.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:18 p.m.