Triple
T28595944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Language Committee |
E723770
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wikimedia community body |
C23975
|
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 community body Context triple: [Language Committee, instanceOf, Wikimedia community body]
-
A.
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.
-
B.
Wikimedia governance mechanism
chosen
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.
-
C.
Wikimedia feature
A Wikimedia feature is a distinct functionality or tool within Wikimedia platforms that enhances content creation, editing, navigation, collaboration, or user experience.
-
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 namespace
A Wikimedia namespace is a designated category within Wikimedia projects that organizes pages by their function or content type, such as articles, user pages, or templates, using specific prefixes.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:21 a.m.