Triple
T36485565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbus External Payload Facility |
E898924
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scientific research platform |
C52634
|
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 platform Context triple: [Columbus External Payload Facility, instanceOf, scientific research platform]
-
A.
scientific informatics platform
A scientific informatics platform is an integrated software environment that enables researchers to collect, manage, analyze, and share scientific data and workflows across experiments, instruments, and teams.
-
B.
scientific instrument platform
chosen
A scientific instrument platform is a configurable hardware and software framework that supports the integration, control, and data acquisition of multiple scientific instruments for experimental or observational research.
-
C.
scientific research support program
A scientific research support program is an organized initiative that provides resources, funding, infrastructure, and guidance to facilitate the planning, execution, and dissemination of scientific studies.
-
D.
online research platform
An online research platform is a web-based system that enables users to search, access, organize, and analyze scholarly or domain-specific information and data.
-
E.
scientific research programme
A scientific research programme is a structured, long-term framework of theories, methods, and guiding assumptions that directs and organizes systematic investigation within a particular field of inquiry.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.