Triple
T7959038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Frederick, Margrave of Brandenburg-Ansbach |
E184813
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Franconian ruler |
C12473
|
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: Franconian ruler Context triple: [John Frederick, Margrave of Brandenburg-Ansbach, instanceOf, Franconian ruler]
-
A.
Bavarian monarch
A Bavarian monarch is the sovereign ruler of Bavaria, historically holding supreme political authority and symbolic leadership over the Bavarian state and its people.
-
B.
Germanic ruler
A Germanic ruler is a sovereign or chieftain from one of the Germanic peoples who exercised political, military, and often religious authority over a tribe, kingdom, or territory in Europe.
-
C.
Bavarian prince
A Bavarian prince is a male member of the royal or formerly ruling house of Bavaria, traditionally holding hereditary titles, privileges, and social status within the region’s historical monarchy.
-
D.
King of Germany
The King of Germany is a conceptual class representing a sovereign monarch who historically ruled over the German kingdom within the Holy Roman Empire, embodying supreme political and symbolic authority over its territories and subjects.
-
E.
prince of the Holy Roman Empire
chosen
A prince of the Holy Roman Empire was a secular or ecclesiastical ruler who held immediate authority under the emperor, possessing territorial sovereignty and a vote in the Imperial Diet.
- 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_69ca8293a2388190aace944d7ed9c0c0 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:11 p.m.