Triple
T28227274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulations of Shanghai Municipality on Public Security Management |
E711622
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public security regulation |
C19707
|
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: public security regulation Context triple: [Regulations of Shanghai Municipality on Public Security Management, instanceOf, public security regulation]
-
A.
securities regulation law
Securities regulation law is the body of rules and principles governing the issuance, trading, disclosure, and oversight of financial instruments such as stocks and bonds to protect investors and maintain fair, efficient markets.
-
B.
security legislation
chosen
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.
-
C.
regulations
Regulations are authoritative rules or directives established by a governing body to control, manage, or guide behaviors and processes within a specific domain.
-
D.
safety regulation
A safety regulation is a formal rule or standard established by authorities or organizations to prevent harm, reduce risk, and protect people, property, and the environment in specific activities or industries.
-
E.
financial services regulation
Financial services regulation encompasses the laws, rules, and supervisory frameworks that govern financial institutions and markets to ensure stability, integrity, consumer protection, and fair competition.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:50 p.m.