Triple
T464494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesla Model 3 |
E8414
|
entity |
| Predicate | powertrainLocation |
P14986
|
FINISHED |
| Object | electric motor(s) mounted between axles |
—
|
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: electric motor(s) mounted between axles | Statement: [Tesla Model 3, powertrainLocation, electric motor(s) mounted between axles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powertrainLocation Context triple: [Tesla Model 3, powertrainLocation, electric motor(s) mounted between axles]
-
A.
chassis
Indicates that one entity serves as the structural frame or supporting base (chassis) for another entity.
-
B.
electricMotorType
Indicates the specific kind or category of electric motor associated with an entity.
-
C.
batteryPlacement
Indicates the spatial or positional relationship specifying where a battery is located or installed relative to another object or system.
-
D.
offersPowertrain
Indicates that one entity provides or makes available a specific powertrain to another entity or for a particular product.
-
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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efd5b6b48190ae23968135cf6417 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edea1acc81908a72d9f4c43438ea |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef611b9c8190ac5e9174744d9127 |
completed | Feb. 28, 2026, 1:36 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.