Triple
T36568903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willing family |
E902059
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prominent Philadelphia family |
C9457
|
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: prominent Philadelphia family Context triple: [Willing family, instanceOf, prominent Philadelphia family]
-
A.
prominent family
chosen
A prominent family is a socially influential and widely recognized household whose members hold significant power, status, or visibility within a community or society.
-
B.
member of the Penn family
A member of the Penn family is an individual who belongs by birth, marriage, or adoption to the lineage or household identified by the Penn surname.
-
C.
American legal dynasty
A powerful, multigenerational American family whose members have held prominent roles in law, politics, and public service, shaping legal and political institutions over time.
-
D.
member of the du Pont family
A member of the du Pont family is an individual belonging by birth or marriage to the historically prominent American industrial and philanthropic dynasty associated with the DuPont company.
-
E.
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.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.