Triple
T8541482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenya Medical Training and research institutions (general collaboration) |
E202206
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collaborative network |
C20173
|
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: collaborative network Context triple: [Kenya Medical Training and research institutions (general collaboration), instanceOf, collaborative network]
-
A.
collaborative networks
chosen
Collaborative networks are interconnected groups of individuals or organizations that share resources, knowledge, and responsibilities to achieve common goals more effectively than they could independently.
-
B.
regional collaborative network
A regional collaborative network is a structured alliance of organizations, institutions, and stakeholders within a specific geographic area that coordinate resources, knowledge, and activities to address shared goals and regional challenges.
-
C.
collaborative project
A collaborative project is a coordinated effort in which multiple individuals or groups work together, sharing responsibilities, resources, and expertise to achieve a common goal.
-
D.
collaborative online platform
A collaborative online platform is a digital environment that enables multiple users to work together in real time or asynchronously by sharing information, coordinating tasks, and communicating through integrated tools and services.
-
E.
collaborative working group
A collaborative working group is a coordinated team of individuals who share responsibilities, knowledge, and decision-making to achieve a common goal or complete a specific project.
- 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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:18 p.m.