Triple
T28712770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MediaWiki job queue |
E729870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | MediaWiki subsystem |
C54348
|
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: MediaWiki subsystem Context triple: [MediaWiki job queue, instanceOf, MediaWiki subsystem]
-
A.
MediaWiki extension
A MediaWiki extension is a modular add-on that enhances or modifies the core functionality of a MediaWiki installation by introducing new features, integrations, or custom behaviors.
-
B.
MediaWiki feature
A MediaWiki feature is a distinct functionality or tool within the MediaWiki software that enhances content creation, management, navigation, or collaboration on a wiki site.
-
C.
MediaWiki-specific role
A MediaWiki-specific role represents a distinct set of permissions and responsibilities within a MediaWiki installation, defining what actions a user or process can perform in the wiki environment.
-
D.
Wikimedia infrastructure service
chosen
A Wikimedia infrastructure service is a backend system component that provides core technical capabilities—such as storage, networking, authentication, or content delivery—that support the operation, scalability, and reliability of Wikimedia projects.
-
E.
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.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:49 a.m.