Triple
T18165168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home Guard (Cold War revival, 1950s) |
E434873
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | home defence organisation |
C300
|
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: home defence organisation Context triple: [Home Guard (Cold War revival, 1950s), instanceOf, home defence organisation]
-
A.
defense organization
chosen
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
-
B.
air and missile defence force
An air and missile defence force is a military organization responsible for detecting, tracking, and intercepting hostile aircraft and missiles to protect designated airspace, forces, and critical assets.
-
C.
defence estate
A defence estate is the collective portfolio of land, buildings, infrastructure, and facilities owned, leased, or managed by a nation's defence organization to support military operations, training, administration, and logistics.
-
D.
coastal defence
Coastal defence is the set of structures, natural features, and management strategies designed to protect coastlines from erosion, flooding, and storm impacts.
-
E.
border defense system
A border defense system is an integrated network of physical barriers, surveillance technologies, personnel, and response protocols designed to monitor, control, and protect a nation's boundaries from unauthorized crossings and external threats.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:30 a.m.