Triple
T11573935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Medical Association CPT Editorial Panel |
E274456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical coding oversight body |
C437
|
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 coding oversight body Context triple: [American Medical Association CPT Editorial Panel, instanceOf, medical coding oversight body]
-
A.
federal oversight body
A federal oversight body is a government entity responsible for monitoring, evaluating, and enforcing compliance with laws, regulations, and standards across federal agencies or sectors to ensure accountability and integrity.
-
B.
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.
-
C.
medical classification system
A medical classification system is an organized framework that categorizes diseases, conditions, procedures, and related health information using standardized codes to support diagnosis, treatment, research, and healthcare administration.
-
D.
medical organization
chosen
A medical organization is an entity that coordinates healthcare services, resources, and professionals to promote, maintain, or restore people’s health.
-
E.
healthcare accreditation organization
A healthcare accreditation organization is an independent body that evaluates and certifies healthcare providers and institutions against established quality and safety standards to ensure consistent, high-quality patient care.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:38 p.m.