Triple
T31481714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert Brenninkmeijer |
E803162
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of wealthy family |
C23172
|
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: member of wealthy family Context triple: [Albert Brenninkmeijer, instanceOf, member of wealthy family]
-
A.
member of business family
A member of a business family is an individual who belongs to a family that owns, controls, or significantly influences one or more business enterprises, often participating in or being affected by the family’s commercial activities and legacy.
-
B.
member of a famous family
A member of a famous family is an individual whose identity, social status, or public perception is significantly shaped by their familial connection to widely recognized or influential relatives.
-
C.
member of a prominent New York family
A member of a prominent New York family is an individual born into or formally affiliated with a socially, economically, or politically influential lineage based in New York, whose identity and opportunities are shaped by the family’s status, legacy, and network.
-
D.
member of high society
chosen
A member of high society is an individual who belongs to the socially elite upper class, characterized by wealth, influence, refined manners, and participation in exclusive cultural and social circles.
-
E.
member of the Astor family
A member of the Astor family is an individual belonging by birth or marriage to the historically prominent Astor lineage, known for its substantial wealth, social influence, and philanthropic legacy.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:32 p.m.