Triple
T20395901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German 22nd Infantry Division elements |
E500202
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subordinate combat units |
C2497
|
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: subordinate combat units Context triple: [German 22nd Infantry Division elements, instanceOf, subordinate combat units]
-
A.
Major Command Subordinate Unit
A Major Command Subordinate Unit is an organizational entity that operates under a major command, executing its directives and managing assigned missions, resources, and personnel within a defined scope of responsibility.
-
B.
subordinate unified combatant command
A subordinate unified combatant command is a command established by a unified combatant command to conduct operations on a continuing basis within a specific functional or geographic area under the authority of that parent unified command.
-
C.
military unit component
A military unit component is an individual sub-unit or element, such as a squad, platoon, or company, that combines with others to form a larger organized military force.
-
D.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
E.
armored brigade combat team
An armored brigade combat team is a highly mobile, heavily armored combined-arms military formation designed to conduct offensive and defensive ground operations using tanks, mechanized infantry, artillery, and support units.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:28 a.m.