Triple
T17290693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IS-1 |
E419775
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet heavy tank prototype |
C6782
|
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: Soviet heavy tank prototype Context triple: [IS-1, instanceOf, Soviet heavy tank prototype]
-
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.
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.
-
C.
Soviet military equipment
chosen
Soviet military equipment encompasses the weapons, vehicles, and support systems designed and produced by the Soviet Union to equip its armed forces, characterized by rugged construction, mass production, and doctrinal emphasis on large-scale, combined-arms warfare.
-
D.
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.
-
E.
self-propelled howitzer variant
A self-propelled howitzer variant is an armored, mobile artillery platform built on a powered chassis that modifies a base howitzer design for specific roles such as increased firepower, protection, mobility, or specialized mission capabilities.
- 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.