Triple
T33268407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REACH Candidate List of Substances of Very High Concern |
E851712
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory chemical list |
C45696
|
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 chemical list Context triple: [REACH Candidate List of Substances of Very High Concern, instanceOf, regulatory chemical list]
-
A.
regulatory listing
chosen
A regulatory listing is an official record or catalog entry of entities, products, or activities that meet specified regulatory requirements and are recognized or authorized by a governing body.
-
B.
chemical inventory
A chemical inventory is a systematically organized record of all chemical substances held by an organization, including their quantities, locations, hazards, and regulatory information, to support safe handling, compliance, and efficient resource management.
-
C.
chemicals control treaty
A chemicals control treaty is an international agreement that regulates the production, use, transfer, and disposal of specific chemicals to protect human health, safety, and the environment.
-
D.
chemical substance
A chemical substance is a form of matter with a specific, uniform chemical composition and distinct properties that cannot be separated into components by physical means.
-
E.
pollutant release and transfer register
A pollutant release and transfer register is a publicly accessible database that systematically records the quantities of specific pollutants released to air, water, and land, or transferred off-site for treatment or disposal, by industrial and other facilities.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:32 a.m.