Triple
T14608683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW M Performance (for i4 M50) |
E342898
|
entity |
| Predicate | wheelOptionsInclude |
P115034
|
FINISHED |
| Object | larger diameter alloy 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: larger diameter alloy wheels | Statement: [BMW M Performance (for i4 M50), wheelOptionsInclude, larger diameter alloy wheels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wheelOptionsInclude Context triple: [BMW M Performance (for i4 M50), wheelOptionsInclude, larger diameter alloy wheels]
-
A.
wheelName
Indicates that an entity has or is associated with a specific name assigned to a wheel.
-
B.
wheelType
Indicates the specific kind or category of wheel associated with an entity.
-
C.
wheelSupplier
Indicates that one entity supplies or provides wheels to another entity.
-
D.
wheelArrangementSystem
Indicates the specific configuration or system by which the wheels of a vehicle or rolling stock are arranged and organized.
-
E.
wheelbaseSharedWith
Indicates that two vehicles have the same wheelbase dimensions or share a common wheelbase platform.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb44d327c8190a8d20568429d0f80 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:25 a.m.