Triple
T9525830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upkeep |
E229757
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military weapon |
C15092
|
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: British military weapon Context triple: [Upkeep, instanceOf, British military weapon]
-
A.
British Army facility
A British Army facility is a location owned, operated, or used by the British Army for purposes such as training, administration, logistics, accommodation, storage, or operational deployment.
-
B.
United Kingdom defence initiative
The United Kingdom defence initiative is a strategic program encompassing policies, capabilities, and collaborative efforts designed to protect the UK's national security interests and enhance its military readiness at home and abroad.
-
C.
Soviet military equipment
Soviet military equipment encompasses the weapons, vehicles, and support systems designed and produced by the Soviet Union to equip its armed forces, characterized by rugged construction, mass production, and doctrinal emphasis on large-scale, combined-arms warfare.
-
D.
military equipment
chosen
Military equipment comprises the specialized weapons, vehicles, protective gear, communication systems, and support tools designed, produced, and used by armed forces to conduct and support combat and defense operations.
-
E.
United Kingdom military position
A United Kingdom military position is a specific role or rank within the British Armed Forces, defined by its responsibilities, authority, and place in the military hierarchy.
- 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 7:59 p.m.