Triple
T13563416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maximilian III, Archduke of Austria |
E323969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Grand Master of the Teutonic Order |
C33219
|
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: Grand Master of the Teutonic Order Context triple: [Maximilian III, Archduke of Austria, instanceOf, Grand Master of the Teutonic Order]
-
A.
Grand Master of the Knights Hospitaller
The Grand Master of the Knights Hospitaller is the supreme leader and chief administrator of the Order, responsible for its spiritual direction, military command, and governance of its territories and members.
-
B.
Third Marshal of the Riddermark
The Third Marshal of the Riddermark is a high-ranking Rohirrim military commander responsible for leading one of Rohan’s primary field armies and defending a designated region of the Riddermark.
-
C.
Duke of Prussia
The Duke of Prussia was a hereditary noble title held by the rulers of the Duchy of Prussia, originally a fief of the Polish Crown that later became the core territory of the Kingdom of Prussia.
-
D.
Grand Duke of Lithuania
The Grand Duke of Lithuania was the sovereign ruler of the Grand Duchy of Lithuania, holding supreme political, military, and judicial authority over its territories and often engaging in dynastic unions with neighboring states.
-
E.
Grand Duke of Lithuania
The Grand Duke of Lithuania was the sovereign ruler of the Grand Duchy of Lithuania, holding supreme political, military, and judicial authority over its territories and often engaging in dynastic unions and alliances with neighboring states.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:47 p.m.