Triple
T1101276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee for Medicinal Products for Veterinary Use |
E24385
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory committee |
C5824
|
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 committee Context triple: [Committee for Medicinal Products for Veterinary Use, instanceOf, regulatory committee]
-
A.
regulatory authority
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.
government committee
A government committee is a formally established group of officials or representatives tasked with studying specific issues, developing recommendations, and overseeing particular areas of public policy or administration.
-
C.
self-regulatory organization
A self-regulatory organization is an entity, typically within a specific industry or profession, that creates and enforces rules and standards for its members to promote fair, ethical, and orderly conduct, often under the oversight of a governmental authority.
-
D.
governing council
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
E.
scientific committee
chosen
A scientific committee is a group of experts who collaboratively evaluate, guide, and make decisions on scientific matters, such as research quality, funding, ethics, and strategic priorities.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:43 p.m.