Triple
T7034686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III Corps (Finland) |
E163352
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Finnish Army formation |
C20689
|
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: Finnish Army formation Context triple: [III Corps (Finland), instanceOf, Finnish Army formation]
-
A.
Indian Army formation
An Indian Army formation is an organized military unit or grouping, such as a corps, division, brigade, or battalion, structured for command, control, and execution of land-based operations within the Indian Army.
-
B.
Canadian Army formation
A Canadian Army formation is an organized, hierarchical grouping of military units (such as brigades or divisions) structured to conduct land operations under a unified command within the Canadian Armed Forces.
-
C.
formation of the Russian Armed Forces
The formation of the Russian Armed Forces is the historical and organizational process through which Russia established, structured, and developed its modern military institutions, branches, and command systems following the dissolution of the Soviet Union.
-
D.
French Army formation
A French Army formation is an organized military unit or grouping within the French Army, structured and equipped to conduct specific operational, tactical, or administrative functions.
-
E.
Indian Armed Forces formation
An Indian Armed Forces formation is an organized military unit or grouping, such as a command, corps, division, brigade, or equivalent structure, established to plan, coordinate, and conduct operations within the Indian Army, Navy, or Air Force.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:36 p.m.