Triple
T23139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Science and Technology Centers |
E460
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research collaboration programs |
C343
|
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 collaboration programs Context triple: [Science and Technology Centers, instanceOf, research collaboration programs]
-
A.
university collaboration
University collaboration is the structured partnership between universities and external entities (such as other academic institutions, industry, government, or communities) to jointly pursue research, education, innovation, and resource sharing.
-
B.
research grant program
A research grant program is a structured funding initiative that provides financial support to researchers or institutions to conduct specific scholarly, scientific, or creative projects aligned with defined goals and priorities.
-
C.
research consortium
chosen
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
-
D.
research project
A research project is a structured, systematic investigation designed to answer specific questions or test hypotheses by collecting, analyzing, and interpreting data within a defined scope and timeframe.
-
E.
research fellowship
A research fellowship is a funded, time-limited academic or professional position that supports an individual in conducting specialized research, often under the mentorship of senior experts.
- 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_69a243b4ac2c8190b93c303df797b7b2 |
completed | Feb. 28, 2026, 1:24 a.m. |
Created at: Feb. 28, 2026, 1:34 a.m.