Triple
T3767693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Certificates of Suitability |
E82718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pharmaceutical regulatory document |
C3993
|
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: pharmaceutical regulatory document Context triple: [Certificates of Suitability, instanceOf, pharmaceutical regulatory document]
-
A.
regulatory document
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.
-
B.
pharmaceutical drug
A pharmaceutical drug is a chemically defined substance or combination of substances administered to diagnose, treat, prevent, or alleviate disease or medical conditions in humans or animals.
-
C.
regulatory filing
chosen
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.
-
D.
medicinal product
A medicinal product is a substance or combination of substances presented as having properties for treating or preventing disease in humans or animals, or administered with the aim of restoring, correcting, or modifying physiological functions or making a medical diagnosis.
-
E.
prescription drug
A prescription drug is a regulated medication that can only be legally obtained and used under the authorization of a licensed healthcare provider to diagnose, treat, or prevent specific medical conditions.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:35 p.m.