Triple
T5257324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saab XWD all-wheel-drive system |
E118732
|
entity |
| Predicate | torqueDistribution |
P62551
|
FINISHED |
| Object | front wheels |
—
|
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: front wheels | Statement: [Saab XWD all-wheel-drive system, torqueDistribution, front wheels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torqueDistribution Context triple: [Saab XWD all-wheel-drive system, torqueDistribution, front wheels]
-
A.
torque
Indicates a rotational force applied by one entity on another around a pivot or axis.
-
B.
drivingForce
Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
-
C.
wheelArrangementSystem
Indicates the specific configuration or system by which the wheels of a vehicle or rolling stock are arranged and organized.
-
D.
drivetrainRole
Indicates the functional role or position an entity has within a drivetrain system (e.g., input, transmission, or output component).
-
E.
thrustDistribution
Indicates how thrust or propulsive force is apportioned or spread among different components, directions, or stages within a system.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcced6881909bdb7ac5471a37fe |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7bcabe58819096255672664513b1 |
completed | March 20, 2026, 4:54 p.m. |
Created at: March 20, 2026, 1:50 p.m.