Triple
T31590033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian 1st Armored Division |
E806069
|
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 1st Armored Division, instanceOf, Royal Hungarian Army unit]
-
A.
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.
-
B.
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.
-
C.
hussar regiment
A hussar regiment is a light cavalry military unit, historically composed of fast, lightly armed horsemen used for reconnaissance, raiding, and skirmishing.
-
D.
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.
-
E.
component of the Hungarian Defence Forces
A component of the Hungarian Defence Forces is an organizational unit—such as a branch, service, command, or specialized formation—that contributes specific capabilities and functions to Hungary’s overall military structure and 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:27 p.m.