Triple
T12367527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Rights Protocol Considerations Research Group |
E294910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Internet research body |
C497
|
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: Internet research body Context triple: [Human Rights Protocol Considerations Research Group, instanceOf, Internet research body]
-
A.
intelligence research agency
An intelligence research agency is an organization dedicated to systematically collecting, analyzing, and interpreting information to produce actionable insights for strategic, security, or policy decision-making.
-
B.
research organization
A research organization is an institution that systematically investigates specific questions or problems to generate new knowledge, technologies, or insights, often within scientific, academic, or applied domains.
-
C.
research network
chosen
A research network is a structured system of interconnected researchers, institutions, and resources that collaboratively generate, share, and advance knowledge within and across disciplines.
-
D.
research consortium
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
-
E.
public research institution
A public research institution is a government-funded organization dedicated to advancing knowledge and innovation through systematic investigation, experimentation, and dissemination of findings for the benefit of society.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:54 p.m.