Triple
T33747386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assyrian diaspora from Urmia region |
E864735
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ethnic 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: ethnic diaspora community Context triple: [Assyrian diaspora from Urmia region, instanceOf, ethnic diaspora community]
-
A.
immigrant community
An immigrant community is a social group formed by people who have moved from one country to another, sharing common cultural backgrounds, experiences of migration, and support networks in their new location.
-
B.
transnational community
A transnational community is a network of people who maintain enduring social, economic, political, and cultural ties across national borders, creating a shared sense of belonging that spans multiple countries.
-
C.
Korean diaspora community
A Korean diaspora community is a dispersed group of people of Korean origin who maintain cultural, social, and often economic ties to Korea while adapting to and participating in the societies of their host countries.
-
D.
South Asian diaspora
The South Asian diaspora comprises people of South Asian origin living outside the subcontinent who maintain varying degrees of cultural, economic, and political ties to their ancestral homelands while adapting to and shaping their host societies.
-
E.
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.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.