Triple
T24337950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Federation for Medical Education–recognized bodies |
E613431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory body category |
C1181
|
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: regulatory body category Context triple: [World Federation for Medical Education–recognized bodies, instanceOf, regulatory body category]
-
A.
regulatory authority
chosen
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
-
B.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
C.
regulatory agency component
A regulatory agency component is a modular part of a regulatory body responsible for performing specific oversight, rulemaking, enforcement, or compliance functions within a defined domain.
-
D.
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.
-
E.
standards oversight body
A standards oversight body is an organization responsible for developing, maintaining, and enforcing technical or procedural standards to ensure consistency, quality, and interoperability across a domain.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 1:57 a.m.