Triple
T482982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League of European Research Universities |
E9811
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research university network |
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 university network Context triple: [League of European Research Universities, instanceOf, research university network]
-
A.
research network
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 university system
A research university system is an organized network of higher education institutions coordinated under a central governance structure to advance education, research, and public service across multiple campuses or units.
-
C.
research university
A research university is a higher education institution that prioritizes the creation of new knowledge through extensive research activities while offering a broad range of undergraduate and graduate academic programs.
-
D.
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.
-
E.
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.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.