Triple
T5668590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfa Romeo 75 |
E124916
|
entity |
| Predicate | transaxleLayout |
P14986
|
FINISHED |
| Object | rear-mounted transaxle |
—
|
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-mounted transaxle | Statement: [Alfa Romeo 75, transaxleLayout, rear-mounted transaxle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transaxleLayout Context triple: [Alfa Romeo 75, transaxleLayout, rear-mounted transaxle]
-
A.
powertrainLocation
chosen
Indicates the physical placement or mounting position of a vehicle’s powertrain relative to the rest of the vehicle.
-
B.
vehicleLayout
Indicates how the components or seating within a vehicle are arranged or configured relative to each other.
-
C.
wheelArrangementSystem
Indicates the specific configuration or system by which the wheels of a vehicle or rolling stock are arranged and organized.
-
D.
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.
-
E.
powertrainComponentOf
Indicates that one entity is a component or subsystem that forms part of the powertrain of another entity.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.