Triple

T34033161
Position Surface form Disambiguated ID Type / Status
Subject Archduke Louis of Austria (son of Ferdinand I) E872714 entity
Predicate instanceOf P0 FINISHED
Object Austrian military leader C15885 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: Austrian military leader
Context triple: [Archduke Louis of Austria (son of Ferdinand I), instanceOf, Austrian military leader]
  • A. Austro-Hungarian military officer
    An Austro-Hungarian military officer was a commissioned leader in the armed forces of the Austro-Hungarian Empire, responsible for commanding troops, implementing imperial military policy, and upholding the dual monarchy’s authority across its diverse territories.
  • B. Austrian general chosen
    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.
  • C. Hungarian military leader
    A Hungarian military leader is a high-ranking commander from Hungary responsible for planning, directing, and overseeing military operations and forces in defense of national or allied interests.
  • D. Bavarian military officer
    A Bavarian military officer is a commissioned leader from the historical Kingdom or modern state of Bavaria, responsible for commanding troops, executing military strategy, and upholding regional and national defense duties within the broader German armed forces context.
  • E. Prussian general
    A Prussian general is a high-ranking military officer of the historical Kingdom of Prussia, characterized by rigorous discipline, strategic planning, and leadership in organizing and commanding armies in war.
  • 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_69f349a2527c81909a7cd4bda94d70ad completed April 30, 2026, 12:22 p.m.
Created at: May 1, 2026, 1:51 a.m.