Triple
T30143818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CUPRA |
E766196
|
entity |
| Predicate | vehiclePlatformSource |
P42785
|
FINISHED |
| Object | Volkswagen Group platforms |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Volkswagen Group platforms | Statement: [CUPRA, vehiclePlatformSource, Volkswagen Group platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehiclePlatformSource Context triple: [CUPRA, vehiclePlatformSource, Volkswagen Group platforms]
-
A.
vehicleManufacturerHosted
Indicates that a vehicle manufacturer organized, sponsored, or served as the host for a particular event or activity.
-
B.
vehicleDeveloped
Indicates that an entity (such as a person, organization, or group) created, designed, or otherwise developed a particular vehicle.
-
C.
vehicleBase
Indicates that one entity serves as the foundational or underlying base for a vehicle-related entity or system.
-
D.
platformModel
chosen
Indicates that one entity serves as the underlying platform or foundational model upon which the other entity is built, operates, or depends.
-
E.
vehicleBrandAssociated
Indicates that there is an association or linkage between a vehicle and a particular brand.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69f67e8a5c908190abdb6c5aadbaee82 |
completed | May 2, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:18 p.m.