Triple
T4566612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brahe family |
E121924
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Danish noble family |
C811
|
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: Danish noble family Context triple: [Brahe family, instanceOf, Danish noble family]
-
A.
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.
-
B.
noble family
chosen
A noble family is a socially and often legally recognized kinship group that holds hereditary titles, privileges, and status within a hierarchical society, typically associated with landownership, political influence, and longstanding lineage.
-
C.
German princely dynasty
A German princely dynasty is a hereditary ruling family from the German-speaking regions of Europe that historically held princely titles, governed territories, and played significant roles in regional and imperial politics.
-
D.
Swedish noble
A Swedish noble is a member of Sweden’s historically privileged aristocratic estate, traditionally holding hereditary titles, social status, and often land or political influence within the Swedish realm.
-
E.
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.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:09 p.m.