Triple
T32988336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HP Vectra |
E844007
|
entity |
| Predicate | includedModelVariants |
—
|
GENERATED |
| Object | HP Vectra VL |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedModelVariants Context triple: [HP Vectra, includedModelVariants, HP Vectra VL]
-
A.
vehicleVariant
chosen
Indicates that one vehicle is a specific version, model, or configuration variant of another related vehicle.
-
B.
resultedInVehicleVariant
Indicates that one event, process, or action led to the creation or emergence of a specific variant of a vehicle.
-
C.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
D.
includesModelsFrom
Indicates that one collection, set, or group contains models that originate from or are derived from another source or collection.
-
E.
carTypeVariant
Indicates that one car type is a specific variant or version of another car type.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.