Triple
T17354619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Toxicology Program |
E421902
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interagency program |
C32722
|
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: interagency program Context triple: [National Toxicology Program, instanceOf, interagency program]
-
A.
intergovernmental programme
An intergovernmental programme is a coordinated set of policies, activities, or initiatives jointly designed, funded, and implemented by multiple governments or international organizations to address shared issues or achieve common goals across borders.
-
B.
interagency committee
An interagency committee is a collaborative body composed of representatives from multiple government agencies formed to coordinate policies, share information, and address cross-cutting issues.
-
C.
interagency coordination arrangement
chosen
An interagency coordination arrangement is a structured agreement or framework that defines how multiple government or organizational agencies collaborate, share information, and align responsibilities to achieve common objectives.
-
D.
interstate agency
An interstate agency is an organization formed by two or more states through a formal agreement to collaboratively manage shared resources, services, or regulatory responsibilities across their borders.
-
E.
intergovernmental partnership
An intergovernmental partnership is a collaborative arrangement in which two or more governments coordinate policies, resources, and actions to address shared issues or achieve common goals.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.