Triple
T10041528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home Guard (Sweden) |
E205306
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of the Swedish Armed Forces |
C27333
|
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: component of the Swedish Armed Forces Context triple: [Home Guard (Sweden), instanceOf, component of the Swedish Armed Forces]
-
A.
Swedish Army regiment
A Swedish Army regiment is a military unit of the Swedish Army responsible for organizing, training, and maintaining combat-ready forces within a specific branch, function, or geographic area.
-
B.
component of the Turkish Armed Forces
A component of the Turkish Armed Forces is an organizational branch or unit, such as the army, navy, air force, or specialized command, that contributes to Turkey’s national defense and military operations.
-
C.
component of the Hungarian Defence Forces
A component of the Hungarian Defence Forces is an organizational unit—such as a branch, service, command, or specialized formation—that contributes specific capabilities and functions to Hungary’s overall military structure and operations.
-
D.
Swedish military designation
A Swedish military designation is a standardized alphanumeric or descriptive label used by Sweden’s armed forces to identify and classify military equipment, units, roles, or systems.
-
E.
branch of the Bundeswehr
A branch of the Bundeswehr is a major organizational component of Germany’s armed forces, such as the Army, Navy, or Air Force, each with distinct roles, capabilities, and responsibilities in national defense.
- F. None of above. chosen
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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 8:55 p.m.