Triple
T35972595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Ordnance Factory Dalmuir |
E1040326
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Ordnance Factory |
C29459
|
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: Royal Ordnance Factory Context triple: [Royal Ordnance Factory Dalmuir, instanceOf, Royal Ordnance Factory]
-
A.
ordnance facility
An ordnance facility is a specialized site where military weapons, ammunition, and related explosive materials are manufactured, stored, maintained, and sometimes tested under controlled conditions.
-
B.
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.
-
C.
munitions facility
chosen
A munitions facility is an industrial site where explosive weapons, ammunition, and related components are manufactured, assembled, stored, and sometimes tested under controlled conditions.
-
D.
Royal Electrical and Mechanical Engineers unit
A Royal Electrical and Mechanical Engineers unit is a military formation responsible for the maintenance, repair, and recovery of the army’s electrical, mechanical, and electronic equipment to ensure operational readiness.
-
E.
Royal Air Force maintenance unit
A Royal Air Force maintenance unit is a specialized organizational entity responsible for the inspection, repair, servicing, and logistical support of RAF aircraft and related equipment to ensure operational readiness and safety.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.