Triple
T20855455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CVR(T) family |
E513467
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tracked reconnaissance vehicle family |
C18625
|
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: tracked reconnaissance vehicle family Context triple: [CVR(T) family, instanceOf, tracked reconnaissance vehicle family]
-
A.
military vehicle family
chosen
A military vehicle family is a group of related combat or support vehicles that share a common platform, components, and design philosophy to fulfill different battlefield roles efficiently.
-
B.
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.
-
C.
tactical support vehicle
A tactical support vehicle is a specialized, often armored, ground platform designed to transport personnel, equipment, and supplies while providing logistical, communications, and limited defensive capabilities in military or law-enforcement operations.
-
D.
tactical military truck
A tactical military truck is a rugged, all-terrain vehicle designed to transport troops, equipment, and supplies in combat and support operations under harsh and hostile conditions.
-
E.
half-track vehicle family
A half-track vehicle family is a group of related military or utility vehicles that combine front wheels with rear tracks to improve off-road mobility while retaining some on-road handling characteristics.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:44 p.m.