Triple
T3857183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuclear Engineering Division facilities |
E90046
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scientific research facility network |
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: scientific research facility network Context triple: [Nuclear Engineering Division facilities, instanceOf, scientific research facility network]
-
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.
National Science Foundation facility
A National Science Foundation facility is a research infrastructure, laboratory, observatory, or center funded or supported by the NSF to enable and advance scientific discovery and education across diverse disciplines.
-
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.
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.
-
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.
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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.