Triple
T27955059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guangdong Provincial Medical Security Bureau |
E703526
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical security authority |
C7955
|
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: medical security authority Context triple: [Guangdong Provincial Medical Security Bureau, instanceOf, medical security authority]
-
A.
medical system
A medical system is an organized framework of people, institutions, technologies, and processes that work together to deliver healthcare services for maintaining and improving individuals’ health.
-
B.
health authority
chosen
A health authority is an organization or governmental body responsible for overseeing, regulating, and coordinating public health services, policies, and programs within a specific jurisdiction.
-
C.
medical organization
A medical organization is an entity that coordinates healthcare services, resources, and professionals to promote, maintain, or restore people’s health.
-
D.
healthcare administration service
A healthcare administration service manages the non-clinical operations of healthcare organizations, including scheduling, billing, compliance, records management, and coordination among providers, payers, and patients to ensure efficient and compliant delivery of care.
-
E.
medical device regulation system
A medical device regulation system is a framework of processes, rules, and oversight mechanisms that govern the evaluation, approval, monitoring, and post-market surveillance of medical devices to ensure their safety, effectiveness, and compliance with regulatory standards.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 7:27 p.m.