Triple
T29754814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Community Affairs Committee |
E753000
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wikimedia Foundation committee |
C54350
|
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 Foundation committee Context triple: [Community Affairs Committee, instanceOf, Wikimedia Foundation committee]
-
A.
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.
-
B.
Wikimedia organizational structure element
chosen
A Wikimedia organizational structure element is a component within the Wikimedia movement’s governance and operational framework, such as committees, affiliates, or roles, that defines responsibilities, decision-making authority, and collaboration pathways.
-
C.
library committee
A library committee is a group of individuals responsible for guiding the development, management, and policies of a library’s collections, services, and resources.
-
D.
Wikimedia Foundation department
A Wikimedia Foundation department is an organizational unit within the Wikimedia Foundation responsible for managing specific functional areas such as engineering, product development, community support, fundraising, or legal affairs to support the Wikimedia projects and mission.
-
E.
Wikimedia feature
A Wikimedia feature is a distinct functionality or tool within Wikimedia platforms that enhances content creation, editing, navigation, collaboration, or user experience.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:56 p.m.