Triple
T20508910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regiment of Foot No. 6 |
E503506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian military unit |
C17809
|
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: Prussian military unit Context triple: [Regiment of Foot No. 6, instanceOf, Prussian military unit]
-
A.
Prussian Army regiment
chosen
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.
-
B.
component of the Prussian Army
A component of the Prussian Army is an organizational subdivision—such as a regiment, corps, or specialized unit—responsible for specific military functions within the broader Prussian military structure.
-
C.
Nazi Germany military unit
A Nazi Germany military unit is an organized formation of armed personnel under the command structure of the Third Reich, created to conduct military operations in support of its expansionist and genocidal objectives during World War II.
-
D.
German Army regiment
A German Army regiment is a mid-sized military unit typically composed of several battalions, providing a structured formation for combat, support, and administrative functions within the German land forces.
-
E.
Bavarian Army unit
A Bavarian Army unit is a military formation originating from the Kingdom or State of Bavaria, organized for combat, support, or administrative roles within the broader structure of the Bavarian or German armed forces.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:36 a.m.