Triple
T19687470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forces of Ferdinand I |
E472749
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Habsburg army |
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: Habsburg army Context triple: [Forces of Ferdinand I, instanceOf, Habsburg army]
-
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.
Parliamentarian army
A Parliamentarian army is a military force organized, funded, and directed by a parliamentary body to wage war or maintain order in support of its political authority and policies.
-
C.
Austrian general
An Austrian general is a high-ranking military officer from Austria responsible for planning, directing, and overseeing large-scale military operations and strategic defense initiatives.
-
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.
French Revolutionary army
The French Revolutionary army was the mass conscripted military force of revolutionary France that combined ideological zeal, innovative organization, and large citizen armies to defend and spread the Revolution across Europe.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:45 p.m.