Triple
T28596351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikimedia Foundation Abstract Wikipedia team |
E723780
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wikimedia Foundation team |
C9208
|
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 team Context triple: [Wikimedia Foundation Abstract Wikipedia team, instanceOf, Wikimedia Foundation team]
-
A.
Wikimedia Foundation department
chosen
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.
-
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 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 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.
-
E.
United Nations team
A United Nations team is a group of international professionals collaboratively working under UN mandates to address global issues such as peace, security, development, and human rights.
- 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:22 a.m.