Triple
T35552852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanzelin of Altenburg |
E1027411
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Alemannic noble |
C62225
|
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: Alemannic noble Context triple: [Lanzelin of Altenburg, instanceOf, Alemannic noble]
-
A.
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.
-
B.
Lombard noble
A Lombard noble is a high-ranking member of the Lombard aristocracy in early medieval Italy, holding land, military authority, and political influence within the Lombard kingdom.
-
C.
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.
-
D.
Austrian noble
An Austrian noble is a member of the historical aristocracy of Austria, typically holding hereditary titles, land, and social privileges within the Habsburg and later Austrian realms.
-
E.
Helvetian noble
A Helvetian noble is a high-ranking member of the ancient Helvetii tribe’s aristocracy, wielding significant political, military, and social influence within their Celtic society.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.