Triple
T23333289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LAV (leisure activity vehicle) |
E591504
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-purpose vehicle type |
C3092
|
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: multi-purpose vehicle type Context triple: [LAV (leisure activity vehicle), instanceOf, multi-purpose vehicle type]
-
A.
tactical vehicle
A tactical vehicle is a specialized, often armored, ground transport designed to support military or law-enforcement operations by providing mobility, protection, and mission-specific capabilities in challenging environments.
-
B.
armored utility vehicle
An armored utility vehicle is a heavily protected, multi-purpose transport platform designed to safely carry personnel, equipment, or cargo through hazardous or combat-prone environments.
-
C.
sport utility vehicle
chosen
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.
-
D.
special-purpose vehicle
A special-purpose vehicle is a legally separate entity created by a parent organization to isolate financial risk and carry out a specific, narrowly defined set of activities or transactions.
-
E.
articulated vehicle
An articulated vehicle is a multi-section vehicle, such as a tractor-trailer or bendy bus, whose segments are connected by a pivoting joint to allow greater maneuverability and load capacity.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:16 p.m.