Triple
T23592663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic humanities research networks |
E582524
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic collaboration |
C47845
|
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 collaboration Context triple: [Nordic humanities research networks, instanceOf, academic collaboration]
-
A.
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.
-
B.
academic work
Academic work is any systematic intellectual effort—such as research, writing, studying, or teaching—conducted within an educational or scholarly context to generate, analyze, or communicate knowledge.
-
C.
academic activity
An academic activity is a structured task or engagement, such as studying, attending classes, conducting research, or completing assignments, undertaken to promote learning and scholarly development.
-
D.
scientific collaboration board
A scientific collaboration board is a shared digital or physical workspace where researchers coordinate projects, exchange data and ideas, track progress, and manage collaborative tasks across institutions and disciplines.
-
E.
mathematical collaboration
Mathematical collaboration is the joint process by which mathematicians share ideas, methods, and insights to develop, refine, and communicate mathematical results that they might not achieve as effectively alone.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:42 p.m.