Triple
T28712592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikimedia movement-wide issues |
E729867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wikimedia movement concept |
C54354
|
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: Wikimedia movement concept Context triple: [Wikimedia movement-wide issues, instanceOf, Wikimedia movement concept]
-
A.
Wikimedia movement participant
A Wikimedia movement participant is an individual or organization that actively contributes to, supports, or advocates for Wikimedia projects and their free knowledge mission through activities such as editing, organizing, developing, or outreach.
-
B.
Wikimedia project
A Wikimedia project is a collaborative, wiki-based initiative hosted by the Wikimedia Foundation that focuses on creating, curating, or providing free knowledge and educational content in a specific domain or format.
-
C.
Wikimedia governance mechanism
A Wikimedia governance mechanism is a structured process, policy, or body through which the Wikimedia movement makes, implements, and enforces decisions about content, conduct, resources, and organizational direction across its projects and affiliates.
-
D.
Wikimedia feature
A Wikimedia feature is a distinct functionality or tool within Wikimedia platforms that enhances content creation, editing, navigation, collaboration, or user experience.
-
E.
Wikimedia movement affiliate type
chosen
A Wikimedia movement affiliate type is a formal category that defines the organizational model, scope, and recognition criteria for groups partnering with the Wikimedia movement, such as chapters, thematic organizations, and user groups.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:49 a.m.