Triple
T17026818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee for the Standardization of the Serbian Language |
E413085
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Serbian organization |
C38674
|
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: Serbian organization Context triple: [Committee for the Standardization of the Serbian Language, instanceOf, Serbian organization]
-
A.
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.
-
B.
Serbian nationalist movement
The Serbian nationalist movement is a political and cultural current centered on promoting Serbian national identity, sovereignty, and interests, often emphasizing historical narratives of statehood, territorial claims, and ethnic solidarity.
-
C.
Rusyn organization
A Rusyn organization is a formal group or institution dedicated to representing, preserving, and promoting the cultural, social, political, or educational interests of the Rusyn people.
-
D.
Sorbian organization
A Sorbian organization is an entity dedicated to preserving, promoting, and representing the culture, language, and interests of the Sorbian minority community.
-
E.
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.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:33 a.m.