Triple
T9234819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW X7 M60i |
E221909
|
entity |
| Predicate | driveSystem |
P68759
|
FINISHED |
| Object | xDrive all-wheel drive |
—
|
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: xDrive all-wheel drive | Statement: [BMW X7 M60i, driveSystem, xDrive all-wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driveSystem Context triple: [BMW X7 M60i, driveSystem, xDrive all-wheel drive]
-
A.
driveMechanism
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
-
B.
drivingForce
Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
-
C.
drivetrainFeature
chosen
Indicates that an entity has a specific characteristic, component, or capability related to its drivetrain system.
-
D.
drivetrainRole
Indicates the functional role or position an entity has within a drivetrain system (e.g., input, transmission, or output component).
-
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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee1cca0c8190bf587f54236c9e45 |
completed | April 1, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:29 p.m.