Triple
T14097712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juliana of Stolberg |
E339295
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 16th-century German noble |
C20512
|
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: 16th-century German noble Context triple: [Juliana of Stolberg, instanceOf, 16th-century German noble]
-
A.
16th-century German person
chosen
A 16th-century German person is an individual who lived in the German-speaking regions of Central Europe between 1501 and 1600, shaped by the cultural, religious, and political transformations of the Renaissance and Reformation eras.
-
B.
Dutch nobleman
A Dutch nobleman is a male member of the Netherlands' hereditary or titular nobility, historically holding social status, privileges, and often land or official positions within Dutch society.
-
C.
17th-century German person
A 17th-century German person is an individual who lived in the German-speaking regions of Central Europe between 1601 and 1700, shaped by the political fragmentation of the Holy Roman Empire, the Thirty Years’ War, and the cultural currents of the Baroque era.
-
D.
Prussian prince
A Prussian prince is a male royal family member of the Kingdom of Prussia, typically holding hereditary titles, political influence, and social prestige within the Prussian and broader German nobility.
-
E.
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.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:22 p.m.