Triple
T6737963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Trailblazer RS |
E154003
|
entity |
| Predicate | hasWheelSize |
P44248
|
FINISHED |
| Object | 18-inch 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: 18-inch alloy wheels | Statement: [Chevrolet Trailblazer RS, hasWheelSize, 18-inch alloy wheels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWheelSize Context triple: [Chevrolet Trailblazer RS, hasWheelSize, 18-inch alloy wheels]
-
A.
formerWheelDiameter
Indicates that one entity was previously the wheel diameter of another entity, but is no longer its current wheel diameter.
-
B.
wheelDiameter
chosen
Indicates the size of a wheel measured across its diameter.
-
C.
driverDiameter
Indicates the size of the circular cross-section of a driver component, typically measured as the distance across its widest point.
-
D.
wheelHeightApprox
Indicates that the height of a wheel is approximately equal to a specified value or to the height of another wheel.
-
E.
tireSize
Indicates the specific size of a tire associated with an object or vehicle.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1850a288190aa7e647fefbb0ede |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:10 p.m.