Triple
T35229437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbian community in Bulgaria |
E1017189
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Serb diaspora community |
C60875
|
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: Serb diaspora community Context triple: [Serbian community in Bulgaria, instanceOf, Serb diaspora community]
-
A.
ethnic diaspora community
chosen
An ethnic diaspora community is a dispersed population of people who share a common ancestral, cultural, or national origin and maintain social, cultural, and often economic ties both within their host societies and with their homeland.
-
B.
Serbian family
A Serbian family is a close-knit kinship group typically characterized by strong intergenerational bonds, respect for elders, shared cultural and religious traditions, and frequent gatherings centered around food, celebration, and mutual support.
-
C.
Eurasian community
A Eurasian community is a social and cultural group formed by people, institutions, and networks that connect and integrate societies across Europe and Asia through shared interests, interactions, and identities.
-
D.
Hungarian diaspora
The Hungarian diaspora comprises ethnic Hungarians and their descendants living outside Hungary, shaped by historical border changes, migration, and cultural preservation abroad.
-
E.
Serbian-American person
A Serbian-American person is an individual of Serbian heritage who lives in, is a citizen of, or strongly identifies with both Serbian and American cultures.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.