Triple
T32040781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axiom Security Systems |
E818213
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | access control solutions provider |
C27280
|
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: access control solutions provider Context triple: [Axiom Security Systems, instanceOf, access control solutions provider]
-
A.
access control systems provider
chosen
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.
-
B.
access control system
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.
-
C.
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.
-
D.
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.
-
E.
security technology company
A security technology company develops and provides advanced tools, systems, and services to protect people, data, and assets from physical and digital threats.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:19 a.m.