Triple
T23525932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type Four platform |
E576432
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | shared car architecture |
C10283
|
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: shared car architecture Context triple: [Type Four platform, instanceOf, shared car architecture]
-
A.
shared vehicle architecture
A shared vehicle architecture is a common, modular platform designed to support multiple vehicle models or types, enabling reuse of components, streamlined engineering, and reduced development costs.
-
B.
automotive architecture
Automotive architecture is the conceptual and structural design framework that defines how a vehicle’s key systems, components, and spatial layout are organized and integrated to meet performance, safety, and user experience goals.
-
C.
Smart vehicle
A smart vehicle is an automobile equipped with advanced sensors, connectivity, and automated systems that enable it to monitor its environment, assist or automate driving tasks, and communicate with other devices or infrastructure to enhance safety, efficiency, and user experience.
-
D.
automotive platform
chosen
An automotive platform is a shared, standardized set of structural, mechanical, and electronic components that underpins multiple vehicle models to streamline development, reduce costs, and enable design flexibility.
-
E.
car rental booking platform
A car rental booking platform is an online system that allows users to search, compare, and reserve rental vehicles from various providers based on location, time, price, and vehicle preferences.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 6:09 p.m.