Triple

T28712821
Position Surface form Disambiguated ID Type / Status
Subject MediaWiki user rights system E729871 entity
Predicate instanceOf P0 FINISHED
Object software access control system C23210 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: software access control system
Context triple: [MediaWiki user rights system, instanceOf, software access control system]
  • A. access control system chosen
    An access control system is a coordinated set of hardware, software, and policies that regulates and monitors who or what can enter, use, or interact with physical or digital resources based on defined permissions.
  • B. mandatory access control system
    A mandatory access control system is a security model in which access to resources is regulated by a central authority based on predefined policies and security labels, rather than by individual user discretion.
  • C. access control systems provider
    An access control systems provider is a company that designs, supplies, installs, and maintains electronic and physical security solutions that regulate and monitor who can enter or use specific locations, resources, or information.
  • D. contactless access system
    A contactless access system is a security solution that grants or denies entry to users through non-physical interaction methods such as RFID cards, mobile credentials, or biometrics, enhancing convenience and hygiene while maintaining controlled access.
  • E. cybersecurity system
    A cybersecurity system is an integrated set of tools, policies, and processes designed to protect digital assets, networks, and data from unauthorized access, attacks, and damage.
  • 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.