Triple
T13945434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 43rd Reconnaissance Regiment |
E335368
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reconnaissance regiment |
C34410
|
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: reconnaissance regiment Context triple: [43rd Reconnaissance Regiment, instanceOf, reconnaissance regiment]
-
A.
armored regiment
An armored regiment is a military unit equipped primarily with tanks and other armored fighting vehicles, organized to conduct offensive and defensive ground combat operations.
-
B.
parachute infantry regiment
A parachute infantry regiment is a military unit composed of soldiers trained and equipped to deploy by parachute into combat zones to conduct airborne assault, seizure, and holding of key objectives behind enemy lines.
-
C.
Panzergrenadier regiment
A Panzergrenadier regiment is a mechanized infantry formation, typically integrated with armored units, designed to conduct rapid, combined-arms operations alongside tanks.
-
D.
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.
-
E.
Canadian Army cavalry regiment
A Canadian Army cavalry regiment is a military unit historically composed of mounted soldiers and now typically equipped with armored vehicles, responsible for reconnaissance, security, and mobile combat operations.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:17 p.m.