Triple
T10262993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | public TSCA Inventory |
E240645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory database |
C4395
|
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 database Context triple: [public TSCA Inventory, instanceOf, regulatory database]
-
A.
biological database
A biological database is an organized, searchable repository that stores, manages, and provides access to biological information such as sequences, structures, functions, and interactions of biomolecules and organisms.
-
B.
legal database
chosen
A legal database is an organized digital repository that stores, indexes, and enables search and retrieval of legal materials such as statutes, case law, regulations, and secondary sources.
-
C.
federal government database
A federal government database is a centralized, secure digital repository used by national government agencies to store, manage, and retrieve official records, data, and information for administrative, regulatory, and public service purposes.
-
D.
federal government database
A federal government database is a centralized, electronically managed collection of structured data maintained by national government agencies to store, process, and retrieve information for administrative, regulatory, and public service purposes.
-
E.
environmental database
An environmental database is a structured collection of data related to natural resources, ecosystems, pollution, climate, and other environmental factors, designed to support analysis, monitoring, and decision-making.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:33 a.m.