Triple
T11420434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World War II military motorcycles |
E270603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military vehicle category |
C30813
|
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: military vehicle category Context triple: [World War II military motorcycles, instanceOf, military vehicle category]
-
A.
armored military vehicle
An armored military vehicle is a heavily protected, often weaponized, ground transport designed to carry personnel or equipment safely through hostile environments.
-
B.
armored vehicle
An armored vehicle is a heavily protected, often weaponized, transport platform designed to safeguard occupants and critical equipment against ballistic, explosive, and chemical threats in hostile environments.
-
C.
military vehicle family
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.
-
D.
military engineering vehicle
A military engineering vehicle is a specialized armored or unarmored platform designed to support combat operations by performing construction, demolition, obstacle breaching, and battlefield mobility or survivability tasks.
-
E.
U.S. military vehicle
A U.S. military vehicle is a government-owned, purpose-built or modified ground, air, or sea platform designed, equipped, and maintained to support United States armed forces missions, including combat, transport, logistics, reconnaissance, and support operations.
- F. None of above. chosen
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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:34 p.m.