Triple
T29849280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gertrude Schuyler |
E758018
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of Van Rensselaer family |
C24915
|
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 Van Rensselaer family Context triple: [Gertrude Schuyler, instanceOf, member of Van Rensselaer family]
-
A.
member of the Van Rensselaer family
chosen
A member of the Van Rensselaer family is an individual belonging to the historically prominent Dutch-descended landowning and political dynasty centered in colonial and early American New York.
-
B.
member of Van Cortlandt family
A member of the Van Cortlandt family is an individual belonging by birth or marriage to the historically prominent Van Cortlandt lineage, known for its social, political, and economic influence in colonial and early American society.
-
C.
member of the Philipse family
A member of the Philipse family is an individual belonging by birth or legal relation to the historically prominent Philipse lineage, sharing its heritage, name, and familial ties.
-
D.
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.
-
E.
member of the Goelet family
A member of the Goelet family is an individual belonging by birth or legal relation to the historically prominent Goelet lineage, known for its substantial real estate holdings and social influence, particularly in New York.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:43 p.m.