Triple
T31587052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Health Professions Council |
E805982
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health professional regulatory body |
C59486
|
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: health professional regulatory body Context triple: [Allied Health Professions Council, instanceOf, health professional regulatory body]
-
A.
health professional
A health professional is a trained and licensed individual who provides services to maintain, improve, or restore people's physical or mental well-being.
-
B.
postgraduate medical education body
A postgraduate medical education body is an organization responsible for overseeing, accrediting, and supporting the training, assessment, and professional development of doctors after they complete their primary medical degree.
-
C.
disciplinary inspection body
A disciplinary inspection body is an organizational unit responsible for monitoring, investigating, and enforcing compliance with rules, ethics, and standards within an institution or system.
-
D.
medical practitioner register
A medical practitioner register is an official, authoritative list that records and maintains the details, qualifications, and licensing status of individuals authorized to practice medicine within a specific jurisdiction.
-
E.
pharmacy regulator
A pharmacy regulator is an authority or organization responsible for overseeing, licensing, and enforcing standards for pharmacies and pharmacists to ensure the safe, ethical, and effective use of medications.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:26 p.m.