Triple
T28502005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rusyn diaspora in North America |
E721258
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carpatho-Rusyn community |
C54148
|
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: Carpatho-Rusyn community Context triple: [Rusyn diaspora in North America, instanceOf, Carpatho-Rusyn community]
-
A.
Ukrainian community abroad
A Ukrainian community abroad is a group of people of Ukrainian origin or identity living outside Ukraine who maintain social ties, cultural traditions, and often organizational structures that preserve and promote Ukrainian heritage in their host countries.
-
B.
Moravian
Moravian: A member or aspect of the Moravian Church or the cultural, historical, and religious traditions associated with the Moravian people, originating from the region of Moravia in Central Europe.
-
C.
Eastern Romance-speaking community
An Eastern Romance-speaking community is a social group whose members primarily use Eastern Romance languages (such as Romanian, Aromanian, Megleno-Romanian, or Istro-Romanian) as a core marker of shared identity, culture, and everyday communication.
-
D.
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.
-
E.
ethnic community in Poland
An ethnic community in Poland is a group of people residing in Poland who share a common ancestry, culture, language, or historical identity distinct from the Polish majority.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:07 a.m.