Triple
T38342482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ansonborough neighborhood |
E1041444
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neighborhood in Charleston, South Carolina |
C64584
|
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: neighborhood in Charleston, South Carolina Context triple: [Ansonborough neighborhood, instanceOf, neighborhood in Charleston, South Carolina]
-
A.
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.
-
B.
New Orleans neighborhood
A New Orleans neighborhood is a distinct urban district within the city characterized by its unique blend of historical architecture, cultural traditions, local cuisine, and community identity shaped by the city’s Creole, French, Spanish, and African-American heritage.
-
C.
town in North Carolina
A town in North Carolina is a municipally incorporated community within the state that provides local governance, services, and regulations for its residents under North Carolina law.
-
D.
neighborhood of Richmond, Virginia
A neighborhood of Richmond, Virginia is a distinct residential or mixed-use area within the city characterized by its own local identity, history, demographics, and community amenities.
-
E.
African-American town
An African-American town is a community or municipality in which African Americans constitute a significant or majority portion of the population, often shaped by shared cultural, historical, and social experiences.
- 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.