Triple
T35350559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW E30 |
E1020865
|
entity |
| Predicate | allWheelDriveVariant |
P68759
|
FINISHED |
| Object | BMW 325iX |
—
|
NE NERFINISHED |
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: BMW 325iX | Statement: [BMW E30, allWheelDriveVariant, BMW 325iX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allWheelDriveVariant Context triple: [BMW E30, allWheelDriveVariant, BMW 325iX]
-
A.
allWheelDriveBrandName
Indicates that a brand name is associated with or used to designate an all-wheel-drive system.
-
B.
driveWheels
Indicates that an entity functions as a wheel or set of wheels that provide driving or propulsive force for a vehicle or mechanism.
-
C.
drivetrainFeature
chosen
Indicates that an entity has a specific characteristic, component, or capability related to its drivetrain system.
-
D.
wheelDriveSystemSupplier
Indicates that one entity supplies or provides the wheel drive system to another entity.
-
E.
hasLeadingWheelArrangement
Indicates the specific configuration of the leading (front) wheels in a vehicle’s or locomotive’s wheel arrangement.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.