Triple
T37782302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarians in Vojvodina |
E941862
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hungarian diaspora community |
C10869
|
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: Hungarian diaspora community Context triple: [Hungarians in Vojvodina, instanceOf, Hungarian diaspora community]
-
A.
Hungarian diaspora
chosen
The Hungarian diaspora comprises ethnic Hungarians and their descendants living outside Hungary, shaped by historical border changes, migration, and cultural preservation abroad.
-
B.
Hungarian emigrant
A Hungarian emigrant is a person who leaves Hungary to reside permanently or long-term in another country, often for economic, political, or personal reasons.
-
C.
Hungarian American
A Hungarian American is a person in the United States who is of full or partial Hungarian ancestry, often maintaining cultural, linguistic, or familial ties to Hungary while living within American society.
-
D.
ethnic diaspora community
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.
-
E.
Carpatho-Rusyn community
The Carpatho-Rusyn community is a stateless East Slavic ethnic group native to the Carpathian Mountain region, united by a distinct language, culture, and religious traditions that span across modern-day Ukraine, Slovakia, Poland, Romania, Hungary, and Serbia.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.