Triple
T18332748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einstein–Szilárd collaboration |
E439186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research partnership |
C40361
|
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 partnership Context triple: [Einstein–Szilárd collaboration, instanceOf, research partnership]
-
A.
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.
-
B.
medical research collaboration
A medical research collaboration is a coordinated partnership among researchers, clinicians, institutions, and sometimes industry or patient groups to jointly design, conduct, and analyze studies that advance medical knowledge and improve health outcomes.
-
C.
research organization
A research organization is an institution that systematically investigates specific questions or problems to generate new knowledge, technologies, or insights, often within scientific, academic, or applied domains.
-
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 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.
- F. None of above. chosen
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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:36 a.m.