Triple
T5932579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICH M4 Common Technical Document |
E131971
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory guideline |
C12268
|
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 guideline Context triple: [ICH M4 Common Technical Document, instanceOf, regulatory guideline]
-
A.
normative guideline
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.
regulatory document
chosen
A regulatory document is an official written instrument issued by an authority that defines, interprets, or enforces rules, standards, or requirements governing specific activities, entities, or domains.
-
C.
regulatory framework
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
-
D.
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.
-
E.
regulatory filing
A regulatory filing is an official document or set of documents submitted to a government or regulatory authority to report required information, demonstrate compliance, or request approval related to an organization’s activities.
- 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.