Triple
T31219591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theron se Verkenningskorps |
E795968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Boer commando unit |
C58618
|
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: Boer commando unit Context triple: [Theron se Verkenningskorps, instanceOf, Boer commando unit]
-
A.
Czechoslovak exile unit
A Czechoslovak exile unit is a military formation composed of Czechoslovak personnel organized outside their occupied homeland, typically under foreign command, to continue armed resistance or fulfill allied military roles.
-
B.
Chindit unit
A Chindit unit is a long-range British-Indian special operations formation used in the Burma Campaign of World War II, trained for deep-penetration jungle warfare behind enemy lines.
-
C.
Freikorps unit
A Freikorps unit is a semi-autonomous, often nationalist paramilitary formation composed largely of ex-soldiers, operating with limited state oversight in post–World War I Germany to combat perceived internal and external enemies.
-
D.
Confederate home guard
The Confederate home guard was a local militia force in the Confederate States during the American Civil War, composed mainly of men exempt from regular military service, tasked with maintaining order, defending home fronts, and enforcing conscription laws.
-
E.
commando engineer unit
A commando engineer unit is a specialized military formation that combines combat-trained commandos with engineering expertise to conduct rapid, high-risk construction, demolition, breaching, and sabotage operations in hostile or contested environments.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:10 p.m.