Triple
T9065025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheinmetall BAE Systems Land |
E217223
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military vehicle manufacturer |
C12194
|
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 manufacturer Context triple: [Rheinmetall BAE Systems Land, instanceOf, military vehicle manufacturer]
-
A.
armoured fighting vehicle manufacturer
chosen
An armoured fighting vehicle manufacturer is a company that designs, engineers, and produces military-grade, heavily protected combat vehicles such as tanks, infantry fighting vehicles, and armoured personnel carriers for armed forces and defense clients.
-
B.
commercial vehicle manufacturer
A commercial vehicle manufacturer is a company that designs, produces, and sells vehicles intended primarily for business use, such as trucks, buses, and vans, to transport goods or passengers.
-
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.
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.
-
E.
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.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:11 p.m.