Triple
T12904640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villeré family |
E308699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prominent Louisiana family |
C30658
|
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 Louisiana family Context triple: [Villeré family, instanceOf, prominent Louisiana family]
-
A.
19th-century New Orleans family
chosen
A 19th-century New Orleans family is a multigenerational household shaped by the city’s unique blend of French, Spanish, African, and American influences, whose daily life reflects the era’s social hierarchies, Catholic traditions, Creole culture, and the economic shifts surrounding slavery, Reconstruction, and the rise of the port city.
-
B.
member of the Lincoln family
A member of the Lincoln family is an individual who is biologically or legally related to Abraham Lincoln or his immediate relatives, forming part of his extended familial lineage.
-
C.
parish of Louisiana
A parish of Louisiana is a primary local government and administrative division in the state, equivalent to a county in other U.S. states, responsible for regional governance, services, and law enforcement.
-
D.
South Carolina family
A South Carolina family is a household unit whose members are connected by blood, marriage, or adoption and who live in or maintain strong social, cultural, and economic ties to the state of South Carolina.
-
E.
member of Zemurray family
A member of the Zemurray family is an individual who is biologically or legally related to the Zemurray lineage, sharing its familial heritage, name, and associated social and historical ties.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:40 p.m.