Triple
T21980183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EPFL research laboratories |
E542816
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research organization unit collection |
C44414
|
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 organization unit collection Context triple: [EPFL research laboratories, instanceOf, research organization unit collection]
-
A.
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.
-
B.
university organizational unit
chosen
A university organizational unit is a formally defined subdivision of a university—such as a college, school, department, or institute—responsible for managing specific academic, administrative, or research functions within the institution.
-
C.
research infrastructure collection
A research infrastructure collection is an organized set of facilities, equipment, data, and services that together support and enable systematic scientific investigation and innovation.
-
D.
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.
-
E.
research team
A research team is a collaborative group of individuals with complementary expertise who systematically investigate questions or problems to generate new knowledge or solutions.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 8:04 p.m.