Triple
T10440395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Research Computing Center |
E246151
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research computing facility |
C13371
|
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 computing facility Context triple: [Research Computing Center, instanceOf, research computing facility]
-
A.
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.
-
B.
computer laboratory
chosen
A computer laboratory is a dedicated room or facility equipped with multiple computers and related technologies, providing users with a controlled environment for computing tasks, instruction, and research.
-
C.
research computer system
A research computer system is a specialized computing environment designed to support complex scientific or academic investigations by providing high-performance processing, large-scale data storage, and advanced analytical tools.
-
D.
research facility area
A research facility area is a designated space within or associated with a research institution where scientific, technical, or experimental activities are conducted, supported, or managed.
-
E.
high-performance computing system
A high-performance computing system is an integrated collection of powerful processors, high-speed interconnects, and optimized software designed to perform large-scale, complex computations at very high speeds.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:15 p.m.