Triple
T13956454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conrad I of Württemberg |
E335675
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval German nobleman |
C2995
|
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 nobleman Context triple: [Conrad I of Württemberg, instanceOf, medieval German nobleman]
-
A.
medieval European noble
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.
-
B.
Bohemian nobleman
A Bohemian nobleman is an aristocrat from the historical Kingdom of Bohemia, distinguished by hereditary titles, landownership, and a role in the region’s political and cultural life.
-
C.
Baltic German noble
A Baltic German noble was a member of the German-speaking hereditary elite in the Baltic provinces (primarily present-day Estonia and Latvia), historically holding significant land, political power, and cultural influence under various ruling empires.
-
D.
member of German nobility
A member of German nobility is an individual belonging to a historically privileged social class in German-speaking regions, typically holding hereditary titles, land, and social status recognized under traditional aristocratic systems.
-
E.
German noble
chosen
A German noble is a member of the historical aristocratic class in German-speaking regions, traditionally holding hereditary titles, land, and social privileges within the feudal and later monarchical systems.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:17 p.m.