Triple
T34884666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сокол (Красноярск) |
E1006110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | спортивный клуб |
C5461
|
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: спортивный клуб Context triple: [Сокол (Красноярск), instanceOf, спортивный клуб]
-
A.
athletic club
chosen
An athletic club is an organized group or facility where individuals participate in sports, fitness, and physical training activities, often with shared resources, coaching, and social events.
-
B.
sports club board
A sports club board is a governing body of elected or appointed individuals responsible for setting policies, making strategic decisions, and overseeing the management and financial health of a sports club.
-
C.
multi-sport club association
A multi-sport club association is an organized entity that oversees, coordinates, and supports multiple sports clubs or departments under a unified structure, providing shared governance, resources, and representation.
-
D.
private club
A private club is an exclusive organization whose membership is restricted and typically requires invitation, sponsorship, or application, offering members specific social, recreational, or professional benefits not available to the general public.
-
E.
sports organization collective
A sports organization collective is a coordinated group of sports entities—such as teams, clubs, leagues, or associations—that collaborate under shared governance, resources, or objectives to promote, manage, and develop athletic activities.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.