Triple
T15542393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helles Barracks |
E370511
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Army training facility |
C9039
|
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 Army training facility Context triple: [Helles Barracks, instanceOf, British Army training facility]
-
A.
British Army facility
chosen
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.
former military training camp
A former military training camp is a decommissioned facility once used to prepare armed forces personnel through drills, exercises, and instruction, now repurposed, abandoned, or preserved for historical or alternative uses.
-
C.
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.
-
D.
British Army position
A British Army position is a specific role or rank within the British Army’s organizational structure, defining an individual’s responsibilities, authority, and place in the military hierarchy.
-
E.
military training institution
A military training institution is an organized establishment dedicated to educating, training, and preparing individuals for service in the armed forces through structured programs in physical fitness, discipline, tactics, and leadership.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:07 a.m.