Triple
T10041455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artillery Regiment (Sweden) |
E205304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regiment of the Swedish Army |
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: regiment of the Swedish Army Context triple: [Artillery Regiment (Sweden), instanceOf, regiment of the Swedish Army]
-
A.
Swedish Army regiment
chosen
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.
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.
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.
-
D.
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.
-
E.
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.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 8:55 p.m.