Triple
T36958613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Armor (Quake Live) |
E914250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armor pickup |
C64502
|
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: armor pickup Context triple: [Red Armor (Quake Live), instanceOf, armor pickup]
-
A.
armored recovery vehicle
An armored recovery vehicle is a heavily protected, tracked or wheeled military support vehicle designed to recover, tow, repair, and maintain disabled or damaged armored fighting vehicles on or near the battlefield.
-
B.
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.
-
C.
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.
-
D.
armored utility vehicle
An armored utility vehicle is a heavily protected, multi-purpose transport platform designed to safely carry personnel, equipment, or cargo through hazardous or combat-prone environments.
-
E.
armoured vehicle component
An armoured vehicle component is a specialized part or subsystem designed to enhance the protection, mobility, firepower, or operational functionality of an armoured vehicle under combat or hazardous conditions.
- F. None of above. chosen
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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.