Triple
T33513291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VIS Regulation |
E858302
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legal act on information systems |
C61392
|
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: legal act on information systems Context triple: [VIS Regulation, instanceOf, legal act on information systems]
-
A.
computing law
Computing law is the body of legal principles, regulations, and case law that governs the development, use, and impact of computer technologies, software, data, and digital networks.
-
B.
legislative information system
A legislative information system is a digital platform that collects, manages, tracks, and provides access to legislative documents, processes, and activities to support lawmakers, staff, and the public.
-
C.
information system
An information system is an organized combination of people, processes, data, and technology designed to collect, process, store, and distribute information to support decision-making and control in an organization.
-
D.
legal information category
A legal information category is a classification that organizes legal content—such as statutes, case law, regulations, or legal commentary—into distinct, searchable groupings based on subject matter, jurisdiction, or document type.
-
E.
security legislation
Security legislation comprises the laws and regulations designed to protect a nation’s security interests by governing activities such as surveillance, data protection, counterterrorism, and the use of security forces.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.