Triple
T17290550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KV tank family |
E419771
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II tank 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: World War II tank family Context triple: [KV tank family, instanceOf, World War II tank family]
-
A.
World War II armoured fighting vehicle
A World War II armoured fighting vehicle is a tracked or wheeled, armored, and typically armed military vehicle designed and used between 1939 and 1945 for frontline combat, support, or reconnaissance roles.
-
B.
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.
-
C.
World War II weapon
A World War II weapon is any tool, device, or system—ranging from small arms and artillery to aircraft, naval vessels, and emerging technologies like rockets and atomic bombs—designed and employed by nations between 1939 and 1945 to inflict damage, gain strategic advantage, or defend against enemy forces.
-
D.
main battle tank
A main battle tank is a heavily armored, highly mobile, front-line combat vehicle that combines powerful direct-fire weaponry with advanced protection and maneuverability to dominate ground engagements.
-
E.
third-generation tank
A third-generation tank is a modern main battle tank characterized by advanced composite armor, powerful smoothbore guns, sophisticated fire-control systems, and enhanced mobility designed for high-intensity, combined-arms warfare.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:40 a.m.