Triple
T34989053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vault-Tec Assisted Targeting System |
E1009331
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | combat system feature |
C3939
|
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: combat system feature Context triple: [Vault-Tec Assisted Targeting System, instanceOf, combat system feature]
-
A.
close-range combat system
A close-range combat system is a coordinated set of mechanics, techniques, and rules that govern how characters engage, interact, and resolve actions in short-distance physical confrontations.
-
B.
weapon system
chosen
A weapon system is an integrated set of components, technologies, and processes designed to detect, engage, and neutralize targets through the controlled application of force.
-
C.
battlefield feature
A battlefield feature is any physical or environmental characteristic of the combat area—such as terrain, obstacles, or man-made structures—that influences tactics, movement, visibility, and the outcome of military engagements.
-
D.
naval combat system component
A naval combat system component is an individual hardware or software element—such as a sensor, weapon, processor, or communication module—that contributes specific functionality to the detection, tracking, engagement, or control capabilities of an integrated maritime warfare system.
-
E.
battle move
A battle move is a discrete action or technique used by a combatant to affect opponents, allies, or the battlefield, typically defined by specific effects, conditions, and resource costs.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.