Triple
T2518286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPT |
E55463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | healthcare billing terminology |
C1782
|
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: healthcare billing terminology Context triple: [CPT, instanceOf, healthcare billing terminology]
-
A.
medical classification system
chosen
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.
-
B.
healthcare interoperability initiative
A healthcare interoperability initiative is a coordinated effort to enable seamless, secure exchange and use of health data across diverse systems, organizations, and technologies to improve care quality, efficiency, and patient outcomes.
-
C.
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.
-
D.
Medicare coverage component
A Medicare coverage component is a distinct part or feature of a Medicare plan that defines specific benefits, services, and cost-sharing arrangements available to beneficiaries.
-
E.
administrative code
Administrative code is a structured set of rules and regulations issued by governmental or organizational authorities to guide, control, and standardize administrative actions and procedures.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:46 p.m.