Triple
T31633422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian 2nd Armored Division |
E807231
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Hungarian Army unit |
C59591
|
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: Royal Hungarian Army unit Context triple: [Hungarian 2nd Armored Division, instanceOf, Royal Hungarian Army unit]
-
A.
Royal Hungarian Army unit
chosen
A Royal Hungarian Army unit is a military formation of the Kingdom of Hungary’s land forces, organized for combat, support, or administrative purposes within the Royal Hungarian Army.
-
B.
Hungarian military personnel
Hungarian military personnel are individuals who serve or have served in Hungary's armed forces, including the army, air force, and other military branches, in roles ranging from enlisted soldiers to high-ranking officers.
-
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.
hussar regiment
A hussar regiment is a light cavalry military unit, historically composed of fast, lightly armed horsemen used for reconnaissance, raiding, and skirmishing.
-
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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:46 p.m.