Triple
T37269265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW R75 |
E924469
|
entity |
| Predicate | sidecarDrive |
P187683
|
FINISHED |
| Object | driven sidecar wheel |
—
|
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: driven sidecar wheel | Statement: [BMW R75, sidecarDrive, driven sidecar wheel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sidecarDrive Context triple: [BMW R75, sidecarDrive, driven sidecar wheel]
-
A.
vehicleInteraction
Indicates an interaction or relationship occurring between two or more vehicles, such as influencing each other’s movement, position, or behavior.
-
B.
rideInteraction
Indicates an interaction where one entity is being transported or carried by another, typically by sitting or standing on or within it during movement.
-
C.
driveAssistFeature
Indicates that one entity provides an assistance feature that helps another entity perform driving-related tasks.
-
D.
vehicleIntegration
Indicates the relationship by which a system, component, or service is incorporated into and made to work cohesively with a vehicle’s hardware, software, or operational environment.
-
E.
driveResult
Indicates the outcome or consequence produced by a driving action or driving-related event.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:15 p.m.