Triple
T24675340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agnese Agnelli |
E610968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Agnelli family |
C49498
|
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 Agnelli family Context triple: [Agnese Agnelli, instanceOf, member of the Agnelli family]
-
A.
member of the Rothschild family
A member of the Rothschild family is an individual belonging by birth or marriage to the historically influential European banking dynasty known for its significant roles in finance, philanthropy, and culture.
-
B.
member of the Savelli family
A member of the Savelli family is an individual belonging to the historically influential Roman noble lineage known for its political, ecclesiastical, and social prominence, particularly during the Middle Ages and Renaissance.
-
C.
Member of the House of Medici
A Member of the House of Medici is an individual belonging to the powerful Florentine banking and political dynasty that significantly influenced Renaissance art, culture, and European politics.
-
D.
Member of the House of Medici
A Member of the House of Medici is an individual belonging to the powerful Florentine banking and political dynasty that significantly influenced European finance, art, and politics from the 15th to 18th centuries.
-
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. 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 3:03 a.m.