Triple
T24801388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeep Wrangler Rubicon 392 |
E620531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-performance off-road SUV variant |
C37603
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: high-performance off-road SUV variant Context triple: [Jeep Wrangler Rubicon 392, instanceOf, high-performance off-road SUV variant]
-
A.
high-performance luxury SUV
A high-performance luxury SUV is a premium sport utility vehicle that combines powerful, sports-car-like acceleration and handling with upscale materials, advanced technology, and a spacious, comfortable interior.
-
B.
sport utility vehicle
A sport utility vehicle is a versatile passenger vehicle that combines elements of on-road cars and off-road trucks, typically offering higher ground clearance, spacious interiors, and optional all-wheel or four-wheel drive for varied driving conditions.
-
C.
off-road vehicle class
chosen
An off-road vehicle class represents a category of vehicles specifically designed and equipped to travel over rough, unpaved, or otherwise challenging terrain beyond standard road conditions.
-
D.
full-size SUV
A full-size SUV is a large sport utility vehicle built on a robust platform that offers three rows of seating, substantial cargo capacity, and strong towing capability for families and heavy-duty use.
-
E.
performance SUV
A performance SUV is a sport utility vehicle engineered to deliver high power, sharp handling, and rapid acceleration while retaining the practicality, space, and versatility of a traditional SUV.
- F. None of above.
Provenance (1 batch)
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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:49 a.m.