Triple
T5932490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICH E6 Good Clinical Practice |
E131969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | clinical research guideline |
C989
|
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: clinical research guideline Context triple: [ICH E6 Good Clinical Practice, instanceOf, clinical research guideline]
-
A.
normative guideline
chosen
A normative guideline is a prescriptive rule or principle that defines how things ought to be done or how people ought to behave within a particular context or system.
-
B.
clinical reference classification
A clinical reference classification is a structured system that organizes medical concepts, diagnoses, procedures, or other health-related information into standardized categories to support consistent documentation, analysis, and communication in healthcare.
-
C.
precision medicine research program
A precision medicine research program is an organized effort that studies how individual differences in genes, environment, and lifestyle can be used to tailor disease prevention, diagnosis, and treatment to specific patient populations.
-
D.
intramural research program
An intramural research program is an organized, institutionally funded initiative in which an organization’s own scientists conduct research on-site using internal facilities and resources.
-
E.
scientific committee
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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4 p.m.