Triple
T33268409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REACH Candidate List of Substances of Very High Concern |
E851712
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inventory of chemicals |
C27814
|
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: inventory of chemicals Context triple: [REACH Candidate List of Substances of Very High Concern, instanceOf, inventory of chemicals]
-
A.
chemical inventory
chosen
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.
-
B.
chemical database
A chemical database is a structured digital repository that stores, organizes, and enables retrieval of detailed information about chemical substances, their properties, reactions, and related data.
-
C.
chemical database provider
A chemical database provider is an organization or service that collects, curates, maintains, and distributes structured information about chemical substances, their properties, structures, and related data for research, regulatory, and industrial use.
-
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.
chemical compound
A chemical compound is a substance formed when two or more different elements are chemically bonded together in fixed proportions, exhibiting properties distinct from its constituent elements.
- 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.