Triple
T28627284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikimedia thematic organizations |
E724557
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wikimedia movement affiliate type |
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 affiliate type Context triple: [Wikimedia thematic organizations, instanceOf, Wikimedia movement affiliate type]
-
A.
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.
-
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.
federated wiki
A federated wiki is a decentralized, collaboratively edited web of interconnected pages where each user can host, fork, and modify content on their own server while still sharing and remixing it across the wider network.
- F. None of above. chosen
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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:36 a.m.