Triple
T32518826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RySG |
E831128
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Registries Stakeholder Group |
C24881
|
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: Registries Stakeholder Group Context triple: [RySG, instanceOf, Registries Stakeholder Group]
-
A.
stakeholder group
chosen
A stakeholder group is a collection of individuals or organizations that share a common interest in, or are affected by, the decisions, activities, or outcomes of a project, organization, or system.
-
B.
public registry of clinical studies
A public registry of clinical studies is an openly accessible database that records key information about planned, ongoing, and completed clinical research to promote transparency, accountability, and informed decision-making.
-
C.
regulatory working group
A regulatory working group is a collaborative body of experts and stakeholders convened to analyze, develop, and recommend policies, standards, or compliance strategies within a specific regulatory domain.
-
D.
group of institutions
A group of institutions is a collection of formally organized entities, such as schools, hospitals, or government bodies, that are associated or coordinated for a common purpose or function.
-
E.
multistakeholder organization
A multistakeholder organization is a collaborative governance structure that brings together diverse actors—such as governments, businesses, civil society, and experts—to jointly make decisions, set standards, or address complex issues of shared concern.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1 a.m.