Triple
T22756559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peugeot 9X8 |
E562858
|
entity |
| Predicate | rearAxleDriveType |
P68759
|
FINISHED |
| Object | internal combustion engine |
—
|
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: internal combustion engine | Statement: [Peugeot 9X8, rearAxleDriveType, internal combustion engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rearAxleDriveType Context triple: [Peugeot 9X8, rearAxleDriveType, internal combustion engine]
-
A.
numberOfAxlesDriven
Indicates the count of axles on a vehicle that are actively powered or driven by the propulsion system.
-
B.
drivetrainFeature
chosen
Indicates that an entity has a specific characteristic, component, or capability related to its drivetrain system.
-
C.
driveWheels
Indicates that an entity functions as a wheel or set of wheels that provide driving or propulsive force for a vehicle or mechanism.
-
D.
secondaryDriveAxle
Indicates that one entity functions as a secondary drive axle in relation to another entity within a mechanical or vehicular drivetrain system.
-
E.
primaryDriveAxle
Indicates that one axle functions as the main source of driving power or torque transmission in a vehicle’s drivetrain.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179bd22588190ac724a656194f5b9 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:25 p.m.