Triple
T31312018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archbishop Anno II of Cologne |
E798488
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval German statesman |
C60540
|
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: medieval German statesman Context triple: [Archbishop Anno II of Cologne, instanceOf, medieval German statesman]
-
A.
Burgundian statesman
A Burgundian statesman is a political leader or high-ranking official who served the interests of the Duchy or County of Burgundy, shaping its domestic governance and foreign policy within late medieval and early Renaissance Europe.
-
B.
13th-century German prelate
A 13th-century German prelate is a high-ranking ecclesiastical official in medieval Germany, such as a bishop or abbot, who held both spiritual authority and significant political influence within the Holy Roman Empire during the 1200s.
-
C.
9th-century German noble
A 9th-century German noble was a member of the hereditary warrior aristocracy in the East Frankish realms, holding land and local authority in exchange for military service and loyalty to the Carolingian king or his successors.
-
D.
Prussian statesman
A Prussian statesman is a political leader or high-ranking government official from the Kingdom of Prussia who shaped its domestic policies, diplomacy, and military strategy, often influencing broader European affairs.
-
E.
German duke
A German duke is a high-ranking nobleman historically ruling or holding hereditary authority over a duchy within the German-speaking territories of the Holy Roman Empire and its successor 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:15 p.m.