Triple
T8259272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Council of Rusyns |
E193151
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Rusyn organization |
C24124
|
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: Rusyn organization Context triple: [World Council of Rusyns, instanceOf, Rusyn organization]
-
A.
Crimean Tatar organization
A Crimean Tatar organization is a formal group or institution established by or for Crimean Tatars to represent their interests, preserve their culture and language, and address social, political, or community issues.
-
B.
Soviet organization
A Soviet organization is an institution, agency, or collective entity established under the governance and ideological framework of the Soviet Union to manage political, economic, social, or military functions.
-
C.
Slovak organization
A Slovak organization is an entity legally established or operating in Slovakia, such as a company, institution, association, or non-profit, that pursues specific economic, social, cultural, or public-interest objectives within the Slovak legal and regulatory framework.
-
D.
Cossack
A Cossack is a member of a traditionally semi-military, self-governing community from the steppes of Eastern Europe, renowned for their horsemanship, warrior culture, and role in regional defense and expansion.
-
E.
Polish resistance organization
A Polish resistance organization is a clandestine group formed in Poland to oppose and undermine occupying or oppressive regimes through coordinated political, military, and intelligence activities.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:49 p.m.