Triple
T29709266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronson Harriman Rumsey |
E751730
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Harriman family |
C56112
|
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 the Harriman family Context triple: [Bronson Harriman Rumsey, instanceOf, member of the Harriman family]
-
A.
member of the Rockefeller family
A member of the Rockefeller family is an individual descended from or closely related to the historically influential American Rockefeller lineage, known for its vast wealth, philanthropy, and impact on industry and public life.
-
B.
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.
-
C.
member of the Mellon family
A member of the Mellon family is an individual belonging by birth or legal relation to the historically prominent American Mellon lineage known for its banking, industrial, and philanthropic influence.
-
D.
member of Roosevelt family
A member of the Roosevelt family is an individual belonging by birth or marriage to the prominent American Roosevelt lineage, historically influential in politics, public service, and social reform.
-
E.
member of the Guggenheim family
A member of the Guggenheim family is an individual belonging by birth or marriage to the prominent American Guggenheim lineage known for its mining fortune, philanthropy, and patronage of modern art and 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:29 p.m.