Triple
T18372673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanford Nano Shared Facilities |
E446223
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | shared research facility |
C63
|
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: shared research facility Context triple: [Stanford Nano Shared Facilities, instanceOf, shared research facility]
-
A.
research facility
chosen
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.
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.
-
C.
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.
-
D.
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.
-
E.
private laboratory
A private laboratory is a non-public scientific facility, typically owned by a company or individual, where controlled experiments, analyses, and research are conducted for proprietary, commercial, or specialized purposes.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:45 a.m.