Triple
T36835668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiger (P) |
E910264
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II military vehicle prototype |
C51033
|
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 military vehicle prototype Context triple: [Tiger (P), instanceOf, World War II military vehicle 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.
military prototype vehicle
chosen
A military prototype vehicle is an experimental, often pre-production combat or support platform designed to test new technologies, capabilities, and configurations before potential adoption into active service.
-
C.
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.
-
D.
6×6 military vehicle
A 6×6 military vehicle is a tactical or logistical ground platform with three powered axles providing six-wheel drive for enhanced off-road mobility, payload capacity, and versatility in combat and support roles.
-
E.
4x4 military vehicle
A 4x4 military vehicle is a rugged, all-terrain, four-wheel-drive platform designed to transport troops, equipment, and supplies under harsh environmental and combat conditions.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.