Triple
T20959545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austro-Hungarian Fifth Army |
E516200
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austro-Hungarian Army formation |
C39785
|
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: Austro-Hungarian Army formation Context triple: [Austro-Hungarian Fifth Army, instanceOf, Austro-Hungarian Army formation]
-
A.
Habsburg military formation
chosen
A Habsburg military formation is an organized unit or arrangement of troops within the armed forces of the Habsburg Monarchy, structured according to its evolving doctrines, hierarchies, and tactical needs from the early modern period through the empire’s dissolution.
-
B.
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.
-
C.
Finnish Army formation
A Finnish Army formation is an organized military unit or grouping, such as a brigade or division, structured to conduct land operations under unified command within Finland’s defense forces.
-
D.
French Army formation
A French Army formation is an organized military unit or grouping within the French Army, structured and equipped to conduct specific operational, tactical, or administrative functions.
-
E.
army formation
An army formation is an organized arrangement of military units and personnel on the battlefield or during maneuvers, designed to optimize command, movement, and combat effectiveness.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 1:30 p.m.