Triple
T8729680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skaraborg Regiment |
E207220
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Swedish Army regiment |
C24985
|
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: Swedish Army regiment Context triple: [Skaraborg Regiment, instanceOf, Swedish Army regiment]
-
A.
Finnish Army formation
A Finnish Army formation is an organized military unit or grouping, such as a brigade or division, structured to conduct land operations under unified command within Finland’s defense forces.
-
B.
Prussian Army regiment
A Prussian Army regiment is a military unit of the Kingdom of Prussia, typically composed of several battalions or squadrons, organized under a unified command structure for tactical, administrative, and ceremonial purposes.
-
C.
Finnish military formation
A Finnish military formation is an organized grouping of Finnish Defence Forces personnel and equipment, structured at various hierarchical levels (such as squad, platoon, company, battalion, brigade, or higher) to conduct coordinated military operations.
-
D.
Swedish general
A Swedish general is a high-ranking military officer from Sweden responsible for leading large-scale army operations, shaping defense strategy, and overseeing the training, organization, and readiness of Swedish land forces.
-
E.
U.S. Army regiment
A U.S. Army regiment is a traditional military unit designation that historically grouped multiple battalions or companies under a common lineage and identity, now used primarily for organizational, administrative, and ceremonial purposes rather than as a primary tactical formation.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:37 p.m.