Triple
T25130727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Research Data Alliance |
E629515
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research data organization |
C49763
|
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: research data organization Context triple: [Research Data Alliance, instanceOf, research data organization]
-
A.
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.
-
B.
research computing organization
A research computing organization is a specialized group that provides advanced computational resources, expertise, and support to enable and accelerate data-intensive and computationally driven research.
-
C.
research data metadata schema
A research data metadata schema is a structured framework that defines standardized elements and relationships for describing, organizing, and enabling discovery and reuse of research data.
-
D.
scientific data archive
A scientific data archive is a structured repository that securely stores, preserves, and provides organized access to research data and associated metadata for long-term reuse and verification.
-
E.
research infrastructure collection
A research infrastructure collection is an organized set of facilities, equipment, data, and services that together support and enable systematic scientific investigation and innovation.
- F. None of above. chosen
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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:28 a.m.