Triple
T3232535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW i3 |
E67772
|
entity |
| Predicate | primaryPowertrain |
P45712
|
FINISHED |
| Object | battery electric |
—
|
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: battery electric | Statement: [BMW i3, primaryPowertrain, battery electric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPowertrain Context triple: [BMW i3, primaryPowertrain, battery electric]
-
A.
powertrainComponentOf
Indicates that one entity is a component or subsystem that forms part of the powertrain of another entity.
-
B.
winnerPowertrainType
Indicates the type of powertrain used by the entity that is identified as the winner in a given context or competition.
-
C.
offersPowertrain
Indicates that one entity provides or makes available a specific powertrain to another entity or for a particular product.
-
D.
powertrainLocation
Indicates the physical placement or mounting position of a vehicle’s powertrain relative to the rest of the vehicle.
-
E.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
- F. None of above. chosen
Provenance (4 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaedb718c8190aae12f763033713a |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0dc2248190a38c40f4e06cd41c |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9d5748190a405c89ec8f30264 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:08 p.m.