Triple
T26627596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALMA Regional Center (Japan node) |
E668398
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research infrastructure support hub |
C45184
|
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 infrastructure support hub Context triple: [ALMA Regional Center (Japan node), instanceOf, research infrastructure support hub]
-
A.
research infrastructure component
A research infrastructure component is a foundational hardware, software, or service element that supports the collection, storage, processing, and sharing of data and tools necessary for conducting and advancing research.
-
B.
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.
-
C.
research support unit
chosen
A research support unit is an organizational entity that provides specialized services, resources, and expertise to facilitate, coordinate, and enhance the planning, execution, and dissemination of research activities.
-
D.
research support community
A research support community is a collaborative network of individuals and resources that provides guidance, feedback, tools, and encouragement to help researchers conduct, improve, and share their work.
-
E.
research facility
A research facility is a specialized institution equipped with laboratories, instruments, and resources where scientists and experts systematically investigate, experiment, and develop new knowledge or technologies.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:23 a.m.