Triple
T1302381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edsel B. Ford II |
E27795
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Ford family |
C6743
|
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 Ford family Context triple: [Edsel B. Ford II, instanceOf, member of the Ford family]
-
A.
member of the Chrysler family
A member of the Chrysler family is an individual who is biologically or legally related to the Chrysler lineage, historically associated with the founders and successors of the Chrysler automotive enterprise.
-
B.
member of the Darwin family
A member of the Darwin family is an individual belonging by birth or marriage to the historically notable Darwin lineage, sharing its familial ties, heritage, and social identity.
-
C.
member of the Kennedy family
A member of the Kennedy family is an individual belonging by birth or marriage to the prominent American political and social dynasty descended from Joseph P. Kennedy Sr. and Rose Fitzgerald Kennedy.
-
D.
member of Darwin–Wedgwood family
A member of the Darwin–Wedgwood family is an individual belonging by birth or marriage to the interconnected English Darwin and Wedgwood lineages, noted for their prominent contributions to science, industry, and culture.
-
E.
member of the Nehru family
A member of the Nehru family is an individual belonging by birth or marriage to the prominent Indian political dynasty descended from Motilal Nehru, historically influential in the country’s independence movement and post-independence governance.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
Created at: March 1, 2026, 7:51 p.m.