Triple
T22587626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Sports Club of the Army (CSKA) |
E564842
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian sports organization |
C25651
|
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: Russian sports organization Context triple: [Central Sports Club of the Army (CSKA), instanceOf, Russian sports organization]
-
A.
Soviet sports society
A Soviet sports society was a state-affiliated mass organization that provided athletic training, facilities, and competitions to workers, students, and military personnel, often linked to specific industries or institutions, to promote physical culture and ideological goals in the USSR.
-
B.
Eurasian sports organization
A Eurasian sports organization is an entity that governs, promotes, and coordinates athletic activities, competitions, and development programs across countries spanning Europe and Asia.
-
C.
organization based in Russia
chosen
An organization based in Russia is any structured group or entity—such as a company, nonprofit, institution, or association—whose primary operations, legal registration, or headquarters are located within the Russian Federation.
-
D.
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.
-
E.
Russian company
A Russian company is a legally registered business entity operating within the Russian Federation’s jurisdiction, subject to its corporate, tax, and regulatory frameworks.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 2:46 p.m.