Triple
T4763234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EUCOR – The European Campus |
E105747
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research collaboration 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: research collaboration network Context triple: [EUCOR – The European Campus, instanceOf, research collaboration network]
-
A.
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.
-
B.
research consortium
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.
-
C.
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.
-
D.
research support community
A research support community is a collaborative network of individuals and resources that provides guidance, feedback, tools, and encouragement to help researchers conduct, improve, and share their work.
-
E.
regional collaborative network
A regional collaborative network is a structured alliance of organizations, institutions, and stakeholders within a specific geographic area that coordinate resources, knowledge, and activities to address shared goals and regional challenges.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:20 p.m.