Triple
T35334295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW sDrive |
E1020410
|
entity |
| Predicate | drivenAxle |
P140850
|
FINISHED |
| Object | rear axle in rear‑wheel‑drive configurations |
—
|
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: rear axle in rear‑wheel‑drive configurations | Statement: [BMW sDrive, drivenAxle, rear axle in rear‑wheel‑drive configurations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivenAxle Context triple: [BMW sDrive, drivenAxle, rear axle in rear‑wheel‑drive configurations]
-
A.
numberOfAxlesDriven
Indicates the count of axles on a vehicle that are actively powered or driven by the propulsion system.
-
B.
primaryDriveAxle
chosen
Indicates that one axle functions as the main source of driving power or torque transmission in a vehicle’s drivetrain.
-
C.
secondaryDriveAxle
Indicates that one entity functions as a secondary drive axle in relation to another entity within a mechanical or vehicular drivetrain system.
-
D.
hasAxleCount
Indicates the number of axles that an object (typically a vehicle or rolling stock) possesses.
-
E.
hasAxleConfiguration
Indicates that an entity is associated with a specific arrangement or configuration of its axles.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.