Triple
T30923011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landgrave of Brabant |
E787779
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | title of nobility in the Low Countries |
C31260
|
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: title of nobility in the Low Countries Context triple: [Landgrave of Brabant, instanceOf, title of nobility in the Low Countries]
-
A.
Dutch noble title
chosen
A Dutch noble title is a hereditary or granted rank within the Netherlands’ nobility system, such as baron, count, or duke, conferring social prestige and sometimes traditional privileges but no formal political power today.
-
B.
Belgian noble title
A Belgian noble title is a hereditary or occasionally life-long honorific rank granted by the Belgian monarchy, conferring social prestige and sometimes ceremonial privileges within the Kingdom of Belgium’s nobility system.
-
C.
member of the nobility of the Low Countries
A member of the nobility of the Low Countries is an individual belonging to the hereditary or formally recognized aristocratic elite of the historical or modern regions comprising present-day Belgium, the Netherlands, and Luxembourg.
-
D.
title of nobility in the Holy Roman Empire
A title of nobility in the Holy Roman Empire was a hereditary or granted rank (such as duke, prince, count, or baron) that conferred social status, legal privileges, and often territorial authority within the Empire’s feudal hierarchy.
-
E.
nobility title
A nobility title is a formal hereditary or granted rank that signifies a person's position and privileges within an aristocratic or feudal social hierarchy.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:51 p.m.