Triple
T11930645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BTR series armored personnel carriers |
E283900
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armored personnel carrier family |
C15396
|
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: armored personnel carrier family Context triple: [BTR series armored personnel carriers, instanceOf, armored personnel carrier family]
-
A.
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.
-
B.
armored fighting vehicle
An armored fighting vehicle is a heavily protected, mobile combat platform designed to engage enemy forces using integrated weapon systems on land.
-
C.
armored military vehicle
chosen
An armored military vehicle is a heavily protected, often weaponized, ground transport designed to carry personnel or equipment safely through hostile environments.
-
D.
armoured fighting vehicle
An armoured fighting vehicle is a heavily protected, mobile combat platform—typically tracked or wheeled—designed to engage enemy forces using integrated weapons systems on the battlefield.
-
E.
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.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:45 p.m.