Triple
T29516295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikimania 2016 |
E748805
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wikimania conference |
C55842
|
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: Wikimania conference Context triple: [Wikimania 2016, instanceOf, Wikimania conference]
-
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.
World Wide Web conference
The World Wide Web conference is an annual international academic and industry event focused on the advancement, research, and standardization of web technologies and applications.
-
C.
Wikimedia organizational structure element
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.
-
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 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.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 4:37 p.m.