Triple
T30087682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International HX Series |
E764641
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heavy-duty vocational truck |
C39905
|
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: heavy-duty vocational truck Context triple: [International HX Series, instanceOf, heavy-duty vocational truck]
-
A.
heavy-duty truck variant
chosen
A heavy-duty truck variant is a specialized configuration of a large commercial vehicle designed to handle high payloads, demanding operating conditions, or specific vocational tasks through tailored chassis, powertrain, and body features.
-
B.
medium-duty truck
A medium-duty truck is a commercial vehicle designed to carry moderate payloads and perform tasks such as local delivery, utility work, and regional hauling, typically falling between light-duty pickups and heavy-duty trucks in size and capacity.
-
C.
full-size pickup truck
A full-size pickup truck is a large, body-on-frame light-duty vehicle with a spacious cab and a full-length open cargo bed designed for towing, hauling, and versatile work or recreational use.
-
D.
cargo vehicle
A cargo vehicle is a motorized or non-motorized transport unit designed primarily for carrying goods, materials, or freight rather than passengers.
-
E.
specialized tractor
A specialized tractor is a purpose-built agricultural vehicle designed with specific attachments, power configurations, and structural features to efficiently perform particular farming tasks such as orchard work, vineyard cultivation, or hillside operations.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:04 p.m.