Triple
T20634964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haldex all-wheel-drive system |
E507052
|
entity |
| Predicate | secondaryDriveAxle |
P140851
|
FINISHED |
| Object | rear axle |
—
|
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 | Statement: [Haldex all-wheel-drive system, secondaryDriveAxle, rear axle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryDriveAxle Context triple: [Haldex all-wheel-drive system, secondaryDriveAxle, rear axle]
-
A.
numberOfAxlesDriven
Indicates the count of axles on a vehicle that are actively powered or driven by the propulsion system.
-
B.
rearAxleRatio
Indicates the numerical gear ratio between the driveshaft and the rear axle, describing how many driveshaft rotations are required for one rotation of the rear wheels.
-
C.
drivetrainCategory
Indicates the type or classification of a vehicle’s drivetrain system (e.g., FWD, RWD, AWD) associated with an entity.
-
D.
drivetrainRole
Indicates the functional role or position an entity has within a drivetrain system (e.g., input, transmission, or output component).
-
E.
frontAxleConfiguration
Indicates the specific structural or mechanical arrangement of the vehicle’s front axle.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0e5fc481909e4f0dd7fb1203fc |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:42 a.m.