Triple
T35794392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John III of Bremen |
E1034787
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Medieval German noble |
C32456
|
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 noble Context triple: [John III of Bremen, instanceOf, Medieval German noble]
-
A.
Alemannic noble
An Alemannic noble is a member of the medieval upper class originating from the Alemannic-speaking regions of Central Europe, holding hereditary titles, land, and political influence within the local feudal hierarchy.
-
B.
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.
-
C.
medieval European noble
chosen
A medieval European noble is a high-ranking member of the feudal aristocracy who holds land granted by a monarch in exchange for military service and governance over vassals and peasants.
-
D.
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.
-
E.
Prussian noble
A Prussian noble is a member of the historically privileged landowning and military aristocracy of the Kingdom of Prussia, characterized by hereditary titles, large estates, and significant influence in governance and the officer corps.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.