Triple
T9234625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW CLAR platform |
E221905
|
entity |
| Predicate | powertrainSupport |
P8242
|
FINISHED |
| Object | internal combustion engine |
—
|
LITERAL FINISHED |
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: internal combustion engine | Statement: [BMW CLAR platform, powertrainSupport, internal combustion engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powertrainSupport Context triple: [BMW CLAR platform, powertrainSupport, internal combustion engine]
-
A.
powertrainComponentOf
Indicates that one entity is a component or subsystem that forms part of the powertrain of another entity.
-
B.
powertrainProduction
Indicates a relationship where an entity is involved in the manufacturing or assembly of a vehicle’s powertrain components.
-
C.
powertrainLocation
Indicates the physical placement or mounting position of a vehicle’s powertrain relative to the rest of the vehicle.
-
D.
offersPowertrain
chosen
Indicates that one entity provides or makes available a specific powertrain to another entity or for a particular product.
-
E.
primaryPowertrain
Indicates the main powertrain system that primarily provides propulsion or drive power for a vehicle or machine.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee1cca0c8190bf587f54236c9e45 |
completed | April 1, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:29 p.m.