Triple
T9810192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leibniz-Rechenzentrum / TUM computer science community |
E238248
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic research community |
C2520
|
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: academic research community Context triple: [Leibniz-Rechenzentrum / TUM computer science community, instanceOf, academic research community]
-
A.
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.
-
B.
intellectual community
chosen
An intellectual community is a group of individuals who share, develop, and critically engage with ideas, knowledge, and inquiry around common interests or disciplines.
-
C.
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.
-
D.
research committee
A research committee is a group of appointed individuals responsible for evaluating, guiding, and overseeing research activities, proposals, and policies within an organization or institution.
-
E.
university research team
A university research team is a collaborative group of faculty, students, and sometimes external partners who systematically investigate specific academic or scientific questions to generate new knowledge and publish their findings.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:30 p.m.