Triple
T38605928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Lalaing |
E934342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Belgian noble house |
C64635
|
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: Belgian noble house Context triple: [House of Lalaing, instanceOf, Belgian noble house]
-
A.
Flemish dynasty
The Flemish dynasty refers to the line of medieval rulers and noble families that governed the County of Flanders and surrounding regions, significantly influencing the political, economic, and cultural development of northwestern Europe.
-
B.
Alsatian noble house
An Alsatian noble house is an aristocratic family originating from the Alsace region, historically holding hereditary titles, lands, and political influence within the shifting sovereignties of France and the Holy Roman Empire.
-
C.
Belgian aristocrat
A Belgian aristocrat is a member of Belgium’s hereditary nobility, typically bearing a noble title, upholding longstanding family traditions, and often participating in the country’s cultural, social, and sometimes political life.
-
D.
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.
-
E.
Dutch patrician family
A Dutch patrician family is a historically prominent, often urban-based lineage belonging to the higher bourgeois elite of the Netherlands, distinguished by long-standing social status, wealth, and influence in commerce, politics, or culture.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.